Per UE network controlled small gap (NCSG) signalling

ABSTRACT

An apparatus of a user equipment (UE) can include processing circuitry configured to encode capability information for transmission within a serving cell of an evolved Node-B (eNB), the capability information indicating the UE supports per UE network controlled small gap (NCSG) operation. A request message is encoded to request a per UE NCSG on a first frequency associated with the serving cell. Configuration information received in response to the request message can be decoded, the configuration information including a NCSG configuration for the NCSG on the first frequency. Measurements can be performed on a second frequency during a measurement gap, the measurement gap configured based on the NCSG configuration. A network message is decoded in response to the capability information, the network message including an indication of the request message for requesting the per UE NCSG on the first frequency.

PRIORITY CLAIM

This application is a U.S. National Stage Filing under 35 U.S.C. 371from International Application No. PCT/US2018/032898, filed May 16,2018, now published as WO 2018/213396, which claims the benefit ofpriority to U.S. Provisional Patent Application Ser. No. 62/506,845,filed May 16, 2017, and entitled “PER USER EQUIPMENT (UE) NETWORKCONTROLLED SMALL GAP (NCSG) SIGNALING WITHOUT PER CC INDICATION.” Eachof which are incorporated herein by reference in their entirety.

TECHNICAL FIELD

Aspects pertain to wireless communications. Some aspects relate towireless networks including 3GPP (Third Generation Partnership Project)networks, 3GPP LTE (Long Term Evolution) networks, 3GPP LTE-A (LTEAdvanced) networks, and fifth-generation (5G) networks including 5G newradio (NR) (or 5G-NR) networks and 5G-LTE networks. Other aspects aredirected to per user equipment (UE) network controlled small gap (NCSG)signalling without per component carrier (CC) indication.

BACKGROUND

Mobile communications have evolved significantly from early voicesystems to today's highly sophisticated integrated communicationplatform. With the increase in different types of devices communicatingwith various network devices, usage of 3GPP LTE systems has increased.The penetration of mobile devices (user equipment or UEs) in modernsociety has continued to drive demand for a wide variety of networkeddevices in a number of disparate environments.

LTE and LTE-Advanced are standards for wireless communications ofhigh-speed data for user equipment (UE) such as mobile telephones. InLTE-Advanced and various wireless systems, carrier aggregation is atechnology according to which multiple carrier signals operating ondifferent frequencies may be used to carry communications for a singleUE, thus increasing the bandwidth available to a single device. In someaspects, carrier aggregation may be used where one or more componentcarriers operate on unlicensed frequencies.

There are emerging interests in the operation of LTE systems in theunlicensed spectrum. As a result, an important enhancement for LTE in3GPP Release 13 has been to enable its operation in the unlicensedspectrum via Licensed-Assisted Access (LAA), which expands the systembandwidth by utilizing the flexible carrier aggregation (CA) frameworkintroduced by the LTE-Advanced system. Rel-13 LAA system focuses on thedesign of downlink operation on unlicensed spectrum via CA, while Rel-14enhanced LAA (eLAA) system focuses on the design of uplink operation onunlicensed spectrum via CA.

The use of networked UEs using 3GPP LTE systems has increased in areasof home and work life. Fifth generation (5G) wireless systems areforthcoming, and are expected to enable even greater speed,connectivity, and usability. Next generation 5G networks are expected toincrease throughput, coverage, and robustness and reduce latency andoperational and capital expenditures. As current cellular networkfrequency is saturated, higher frequencies, such as millimeter wave(mmWave) frequency, can be beneficial due to their high bandwidth.

Potential LTE operation in the unlicensed spectrum includes (and is notlimited to) the LTE operation in the unlicensed spectrum via dualconnectivity (DC), or DC-based LAA, and the standalone LTE system in theunlicensed spectrum, according to which LTE-based technology solelyoperates in unlicensed spectrum without requiring an “anchor” in thelicensed spectrum, called MulteFire. MulteFire combines the performancebenefits of LTE technology with the simplicity of Wi-Fi-likedeployments. Further enhanced operation of LTE systems in the licensedas well as unlicensed spectrum is expected in future releases and 5Gsystems. Such enhanced operations can include techniques to addresssignal measurements during network controlled small gap (NCSG)operation.

BRIEF DESCRIPTION OF THE FIGURES

In the figures, which are not necessarily drawn to scale, like numeralsmay describe similar components in different views. Like numerals havingdifferent letter suffixes may represent different instances of similarcomponents. The figures illustrate generally, by way of example, but notby way of limitation, various aspects discussed in the present document.

FIG. 1A illustrates an architecture of a network in accordance with someaspects.

FIG. 1B is a simplified diagram of an overall next generation (NG)system architecture in accordance with some aspects.

FIG. 1C illustrates an example MulteFireNeutral Host Network (NHN) 5Garchitecture in accordance with some aspects.

FIG. 1D illustrates a functional split between next generation radioaccess network (NG-RAN) and the 5G Core network (5GC) in accordance withsome aspects.

FIG. 1E and FIG. 1F illustrate a non-roaming 5G system architecture inaccordance with some aspects.

FIG. 1G illustrates an example Cellular Internet-of-Things (CIoT)network architecture in accordance with some aspects.

FIG. 1H illustrates an example Service Capability Exposure Function(SCEF) in accordance with some aspects.

FIG. 1I illustrates an example roaming architecture for SCEF inaccordance with some aspects.

FIG. 2 illustrates example components of a device 200 in accordance withsome aspects.

FIG. 3 illustrates example interfaces of baseband circuitry inaccordance with some aspects.

FIG. 4 is an illustration of a control plane protocol stack inaccordance with some aspects.

FIG. 5 is an illustration of a user plane protocol stack in accordancewith some aspects.

FIG. 6 is a block diagram illustrating components, according to someexample aspects, able to read instructions from a machine-readable orcomputer-readable medium (e.g., a non-transitory machine-readablestorage medium) and perform any one or more of the methodologiesdiscussed herein.

FIG. 7 is an illustration of a per UE network controlled small gap(NCSG) in accordance with some aspects.

FIG. 8 is an illustration of NCSG patterns which can be used inconnection with per UE NCSG configuration in accordance with someaspects.

FIG. 9 is an example communication exchange for configuring per UE NCSGin accordance with some aspects.

FIG. 10 illustrates generally a flowchart of example functionalitieswhich can be performed in connection with per UE NCSG configuration andmeasurements, in accordance with some aspects.

FIG. 11 illustrates a block diagram of a communication device such as anevolved Node-B (eNB), a new generation Node-B (gNB), an access point(AP), a wireless station (STA), a mobile station (M S), or a userequipment (UE), in accordance with some aspects.

DETAILED DESCRIPTION

The following description and the drawings sufficiently illustrateaspects to enable those skilled in the art to practice them. Otheraspects may incorporate structural, logical, electrical, process, andother changes. Portions and features of some aspects may be included in,or substituted for, those of other aspects. Aspects set forth in theclaims encompass all available equivalents of those claims.

Any of the radio links described herein may operate according to any oneor more of the following exemplary radio communication technologiesand/or standards including but not limited to: a Global System forMobile Communications (GSM) radio communication technology, a GeneralPacket Radio Service (GPRS) radio communication technology, an EnhancedData Rates for GSM Evolution (EDGE) radio communication technology,and/or a Third Generation Partnership Project (3GPP) radio communicationtechnology, for example Universal Mobile Telecommunications System(UMTS), Freedom of Multimedia Access (FOMA), 3GPP Long Term Evolution(LTE), 3GPP Long Term Evolution Advanced (LTE Advanced), Code divisionmultiple access 2000 (CDMA2000), Cellular Digital Packet Data (CDPD),Mobitex, Third Generation (3G), Circuit Switched Data (CSD), High-SpeedCircuit-Switched Data (HSCSD), Universal Mobile TelecommunicationsSystem (Third Generation) (UMTS (3G)), Wideband Code Division MultipleAccess (Universal Mobile Telecommunications System) (W-CDM A (UMTS)),High Speed Packet Access (HSPA), High-Speed Downlink Packet Access(HSDPA), High-Speed Uplink Packet Access (HSUPA), High Speed PacketAccess Plus (HSPA+), Universal Mobile TelecommunicationsSystem-Time-Division Duplex (UMTS-TDD), Time Division-Code DivisionMultiple Access (TD-CDM A), Time Division-Synchronous Code DivisionMultiple Access (TD-CDMA), 3rd Generation Partnership Project Release 8(Pre-4th Generation) (3GPP Rel. 8 (Pre-4G)), 3GPP Rel. 9 (3rd GenerationPartnership Project Release 9), 3GPP Rel. 10 (3rd Generation PartnershipProject Release 10), 3GPP Rel. 11 (3rd Generation Partnership ProjectRelease 11), 3GPP Rel. 12 (3rd Generation Partnership Project Release12), 3GPP Rel. 13 (3rd Generation Partnership Project Release 13), 3GPPRel. 14 (3rd Generation Partnership Project Release 14), 3GPP Rel. 15(3rd Generation Partnership Project Release 15), 3GPP Rel. 16 (3rdGeneration Partnership Project Release 16), 3GPP Rel. 17 (3rd GenerationPartnership Project Release 17), 3GPP Rel. 18 (3rd GenerationPartnership Project Release 18), 3GPP 5G, 3GPP LTE Extra, LTE-AdvancedPro, LTE Licensed-Assisted Access (LAA), MulteFire, UMTS TerrestrialRadio Access (UTRA), Evolved UMTS Terrestrial Radio Access (E-UTRA),Long Term Evolution Advanced (4th Generation) (LTE Advanced (4G)),cdmaOne (2G), Code division multiple access 2000 (Third generation) (CDMA2000 (3G)), Evolution-Data Optimized or Evolution-Data Only (EV-DO),Advanced MobilePhone System (1st Generation) (AMPS (1G)), Total AccessCommunication System/Extended Total Access Communication System(TACS/ETACS), Digital AMPS (2nd Generation) (D-AMPS (2G)), Push-to-talk(PTT), Mobile Telephone System (M T S), Improved Mobile Telephone System(IMTS), Advanced Mobile Telephone System (AMTS), OLT (Norwegian forOffentlig Landmobil Telefoni, Public Land Mobile Telephony), MTD(Swedish abbreviation for Mobiltelefonisystem D, or Mobile telephonysystem D), Public Automated Land Mobile (Autotel/PALM), ARP (Finnish forAutoradiopuhelin, “car radio phone”), NMT (Nordic Mobile Telephony),High capacity version of NTT (Nippon Telegraph and Telephone) (Hicap),Cellular Digital Packet Data (CDPD), Mobitex, DataTAC, IntegratedDigital Enhanced Network (iDEN), Personal Digital Cellular (PDC),Circuit Switched Data (CSD), Personal Handy-phone System (PHS), WidebandIntegrated Digital Enhanced Network (WiDEN), iBurst, Unlicensed MobileAccess (UM A), also referred to as also referred to as 3GPP GenericAccess Network, or GAN standard), Zigbee, Bluetooth®, Wireless GigabitAlliance (WiGig) standard, mmWave standards in general (wireless systemsoperating at 10-300 GHz and above such as WiGig, IEEE 802.11ad, IEEE802.11ay, and the like), technologies operating above 300 GHz and THzbands, (3GPP/LTE based or IEEE 802.11p and other), Vehicle-to-Vehicle(V2V), Vehicle-to-X (V2X), Vehicle-to-Infrastructure (V2I), andInfrastructure-to-Vehicle (12V) communication technologies, 3GPPcellular V2X, DSRC (Dedicated Short Rang Communications) communicationsystems such as Intelligent-Transport-Systems and others.

Aspects described herein can be used in the context of any spectrummanagement scheme including for example, dedicated licensed spectrum,unlicensed spectrum, (licensed) shared spectrum (such as Licensed SharedAccess (LSA) in 2.3-2.4 GHz, 3.4-3.6 GHz, 3.6-3.8 GHz and furtherfrequencies and Spectrum Access System (SAS) in 3.55-3.7 GHz and furtherfrequencies). Applicable exemplary spectrum bands include IMT(International Mobile Telecommunications) spectrum (including 450-470MHz, 790-960 MHz, 1710-2025 MHz, 2110-2200 MHz, 2300-2400 MHz, 2500-2690MHz, 698-790 MHz, 610-790 MHz, 3400-3600 MHz, to name a few),IMT-advanced spectrum, IMT-2020 spectrum (expected to include 3600-3800MHz, 3.5 GHz bands, 700 MHz bands, bands within the 24.25-86 GHz range,for example), spectrum made available under the Federal CommunicationsCommission's “Spectrum Frontier” 5G initiative (including 27.5-28.35GHz, 29.1-29.25 GHz, 31-31.3 GHz, 37-38.6 GHz, 38.6-40 GHz, 42-42.5 GHz,57-64 GHz, 71-76 GHz, 81-86 GHz and 92-94 GHz, etc), the ITS(Intelligent Transport Systems) band of 5.9 GHz (typically 5.85-5.925GHz) and 63-64 GHz, bands currently allocated to WiGig such as WiGigBand 1 (57.24-59.40 GHz), WiGig Band 2 (59.40-61.56 GHz), WiGig Band 3(61.56-63.72 GHz), and WiGig Band 4 (63.72-65.88 GHz); the 70.2 GHz-71GHz band; any band between 65.88 GHz and 71 GHz; bands currentlyallocated to automotive radar applications such as 76-81 GHz; and futurebands including 94-300 GHz and above. Furthermore, the scheme can beused on a secondary basis on bands such as the TV White Space bands(typically below 790 MHz) where in particular the 400 MHz and 700 MHzbands can be employed. Besides cellular applications, specificapplications for vertical markets may be addressed, such as PMSE(Program Making and Special Events), medical, health, surgery,automotive, low-latency, drones, and the like.

Aspects described herein can also be applied to different Singe Carrieror OFDM flavors (CP-OFDM, SC-FDMA, SC-OFDM, filter bank-basedmulticarrier (FBMC), OFDMA, etc.) and in particular 3GPP NR (New Radio)by allocating the OFDM carrier data bit vectors to the correspondingsymbol resources.

FIG. 1A illustrates an architecture of a network in accordance with someaspects. The network 140A is shown to include a user equipment (UE) 101and a UE 102. The UEs 101 and 102 are illustrated as smartphones (e.g.,handheld touchscreen mobile computing devices connectable to one or morecellular networks), but may also comprise any mobile or non-mobilecomputing device, such as Personal Data Assistants (PDAs), pagers,laptop computers, desktop computers, wireless handsets, drones, or anyother computing device including a wired and/or wireless communicationsinterface.

In some aspects, any of the UEs 101 and 102 can comprise anInternet-of-Things (IoT) UE or a Cellular IoT (CIoT) UE, which cancomprise a network access layer designed for low-powerIoT applicationsutilizing short-lived UE connections. In some aspects, any of the UEs101 and 102 can include a narrowband (NB) IoT UE (e.g., such as anenhanced NB-IoT (eNB-IoT) UE and Further Enhanced (FeNB-IoT) UE). An IoTUE can utilize technologies such as machine-to-machine (M2M) ormachine-type communications (MTC) for exchanging data with an MTC serveror device via a public land mobile network (PLMN), Proximity-BasedService (ProSe) or device-to-device (D2D) communication, sensornetworks, or IoT networks. The M2M or MTC exchange of data may be amachine-initiated exchange of data. An IoT network includesinterconnecting IoT UEs, which may include uniquely identifiableembedded computing devices (within the Internet infrastructure), withshort-lived connections. The IoT UEs may execute background applications(e.g., keep-alive messages, status updates, etc.) to facilitate theconnections of the IoT network.

In some aspects, NB-IoT devices can be configured to operate in a singlephysical resource block (PRB) and may be instructed to retune twodifferent PRBs within the system bandwidth. In some aspects, an eNB-IoTUE can be configured to acquire system information in one PRB, and thenit can retune to a different PRB to receive or transmit data.

In some aspects, any of the UEs 101 and 102 can include enhanced MTC(eMTC) UEs or further enhanced MTC (FeMTC) UEs.

The UEs 101 and 102 may be configured to connect, e.g., communicativelycouple, with a radio access network (RAN) 110. The RAN 110 may be, forexample, an Evolved Universal Mobile Telecommunications System (UMTS)Terrestrial Radio Access Network (E-UTRAN), a NextGen RAN (NG RAN), orsome other type of RAN. The UEs 101 and 102 utilize connections 103 and104, respectively, each of which comprises a physical communicationsinterface or layer (discussed in further detail below); in this example,the connections 103 and 104 are illustrated as an air interface toenable communicative coupling and can be consistent with cellularcommunications protocols, such as a Global System for MobileCommunications (GSM) protocol, a code-division multiple access (CDMA)network protocol, a Push-to-Talk (PTT) protocol, a PTT over Cellular(POC) protocol, a Universal Mobile Telecommunications System (UMTS)protocol, a 3GPP Long Term Evolution (LTE) protocol, a fifth generation(5G) protocol, a New Radio (NR) protocol, and the like.

In some aspects, the network 140A can include a core network (CN) 120.Various aspects of NG RAN and NG Core are discussed herein in referenceto, e.g., FIG. 1B, FIG. 1C, FIG. 1D, FIG. 1E, FIG. 1F, and FIG. 1G.

In an aspect, the UEs 101 and 102 may further directly exchangecommunication data via a ProSe interface 105. The ProSe interface 105may alternatively be referred to as a sidelink interface comprising oneor more logical channels, including but not limited to a PhysicalSidelink Control Channel (PSCCH), a Physical Sidelink Shared Channel(PSSCH), a Physical Sidelink Discovery Channel (PSDCH), and a PhysicalSidelink Broadcast Channel (PSBCH).

The UE 102 is shown to be configured to access an access point (AP) 106via connection 107. The connection 107 can comprise a local wirelessconnection, such as, for example, a connection consistent with any IEEE802.11 protocol, according to which the AP 106 can comprise a wirelessfidelity (WiFi®) router. In this example, the AP 106 is shown to beconnected to the Internet without connecting to the core network of thewireless system (described in further detail below).

The RAN 110 can include one or more access nodes that enable theconnections 103 and 104. These access nodes (ANs) can be referred to asbase stations (BSs), NodeBs, evolved NodeBs (eNBs), Next GenerationNodeBs (gNBs), RAN nodes, and the like, and can comprise ground stations(e.g., terrestrial access points) or satellite stations providingcoverage within a geographic area (e.g., a cell). In some aspects, thecommunication nodes 111 and 112 can be transmission/reception points(TRPs). In instances when the communication nodes 111 and 112 are NodeBs(e.g., eNBs or gNBs), one or more TRPs can function within thecommunication cell of the NodeBs. The RAN 110 may include one or moreRAN nodes for providing macrocells, e.g., macro RAN node 111, and one ormore RAN nodes for providing femtocells or picocells (e.g., cells havingsmaller coverage areas, smaller user capacity, or higher bandwidthcompared to macrocells), e.g., low power (LP) RAN node 112.

Any of the RAN nodes 111 and 112 can terminate the air interfaceprotocol and can be the first point of contact for the UEs 101 and 102.In some aspects, any of the RAN nodes 111 and 112 can fulfill variouslogical functions for the RAN 110 including but not limited to, radionetwork controller (RNC) functions such as radio bearer management,uplink and downlink dynamic radio resource management and data packetscheduling and mobility management. In an example, any of the nodes 111and/or 112 can be a new generation node-B (gNB), an evolved node-B(eNB), or another type of RAN node.

In accordance with some aspects, the UEs 101 and 102 can be configuredto communicate using Orthogonal Frequency-Division Multiplexing (OFDM)communication signals with each other or with any of the RAN nodes 111and 112 over a multicarrier communication channel in accordance variouscommunication techniques, such as, but not limited to, an OrthogonalFrequency-Division Multiple Access (OFDMA) communication technique(e.g., for downlink communications) or a Single Carrier FrequencyDivision Multiple Access (SC-FDMA) communication technique (e.g., foruplink and ProSe for sidelink communications), although such aspects arenot required. The OFDM signals can comprise a plurality of orthogonalsubcarriers.

In some aspects, a downlink resource grid can be used for downlinktransmissions from any of the RAN nodes 111 and 112 to the UEs 101 and102, while uplink transmissions can utilize similar techniques. The gridcan be a time-frequency grid, called a resource grid or time-frequencyresource grid, which is the physical resource in the downlink in eachslot. Such a time-frequency plane representation may be used for OFDMsystems, which makes it applicable for radio resource allocation. Eachcolumn and each row of the resource grid may correspond to one OFDMsymbol and one OFDM subcarrier, respectively. The duration of theresource grid in the time domain may correspond to one slot in a radioframe. The smallest time-frequency unit in a resource grid may bedenoted as a resource element. Each resource grid may comprise a numberof resource blocks, which describe mapping of certain physical channelsto resource elements. Each resource block may comprise a collection ofresource elements; in the frequency domain, this may, in some aspects,represent the smallest quantity of resources that currently can beallocated. There may be several different physical downlink channelsthat are conveyed using such resource blocks.

The physical downlink shared channel (PDSCH) may carry user data andhigher-layer signaling to the UEs 101 and 102. The physical downlinkcontrol channel (PDCCH) may carry information about the transport formatand resource allocations related to the PDSCH channel, among otherthing. It may also inform the UEs 101 and 102 about the transportformat, resource allocation, and H-ARQ (Hybrid Automatic Repeat Request)information related to the uplink shared channel. Typically, downlinkscheduling (assigning control and shared channel resource blocks to theUE 102 within a cell) may be performed at any of the RAN nodes 111 and112 based on channel quality information fed back from any of the UEs101 and 102. The downlink resource assignment information may be sent onthe PDCCH used for (e.g., assigned to) each of the UEs 101 and 102.

The PDCCH may use control channel elements (CCEs) to convey the controlinformation. Before being mapped to resource elements, the PDCCHcomplex-valued symbols may first be organized into quadruplets, whichmay then be permuted using a sub-block interleaver for rate matchingEach PDCCH may be transmitted using one or more of these CCEs, whereeach CCE may correspond to nine sets of four physical resource elementsknown as resource element groups (REGs). Four Quadrature Phase ShiftKeying (QPSK) symbols may be mapped to each REG. The PDCCH can betransmitted using one or more CCEs, depending on the size of thedownlink control information (DCI) and the channel condition. There canbe four or more different PDCCH formats defined in LTE with differentnumbers of CCEs (e.g., aggregation level, L=1, 2, 4, or 8).

Some aspects may use concepts for resource allocation for controlchannel information that are an extension of the above-describedconcepts. For example, some aspects may utilize an enhanced physicaldownlink control channel (EPDCCH) that uses PDSCH resources for controlinformation transmission. The EPDCCH may be transmitted using one ormore enhanced control channel elements (ECCEs). Similar to above, eachECCE may correspond to nine sets of four physical resource elementsknown as an enhanced resource element groups (EREGs). An ECCE may haveother numbers of EREGs according to some arrangements.

The RAN 110 is shown to be communicatively coupled to a core network(CN) 120 via an S1 interface 113. In aspects, the CN 120 may be anevolved packet core (EPC) network, a NextGen Packet Core (NPC) network,or some other type of CN (e.g., as illustrated in reference to FIGS.1B-1I). In this aspect, the S1 interface 113 is split into two parts:the S1-U interface 114, which carries traffic data between the RAN nodes111 and 112 and the serving gateway (S-GW) 122, and the S1-mobilitymanagement entity (MME) interface 115, which is a signaling interfacebetween the RAN nodes 111 and 112 and MMEs 121.

In this aspect, the CN 120 comprises the MMEs 121, the S-GW 122, thePacket Data Network (PDN) Gateway (P-GW) 123, and a home subscriberserver (HSS) 124. The MMEs 121 may be similar in function to the controlplane of legacy Serving General Packet Radio Service (GPRS) SupportNodes (SGSN). The MMEs 121 may manage mobility aspects in access such asgateway selection and tracking area list management. The HSS 124 maycomprise a database for network users, including subscription-relatedinformation to support the network entities' handling of communicationsessions. The CN 120 may comprise one or several HSSs 124, depending onthe number of mobile subscribers, on the capacity of the equipment, onthe organization of the network, etc. For example, the HSS 124 canprovide support for routing/roaming authentication, authorization,naming/addressing resolution, location dependencies, etc.

The S-GW 122 may terminate the S1 interface 113 towards the RAN 110, androutes data packets between the RAN 110 and the CN 120. In addition, theS-GW 122 may be a local mobility anchor point for inter-RAN nodehandovers and also may provide an anchor for inter-3GPP mobility. Otherresponsibilities of the S-GW 122 may include lawful intercept, chargingand some policy enforcement.

The P-GW 123 may terminate a SGi interface toward a PDN. The P-GW 123may route data packets between the EPC network 120 and external networkssuch as a network including the application server 184 (alternativelyreferred to as application function (AF)) via an Internet Protocol (IP)interface 125. The P-GW 123 can also communicate data to other externalnetworks 131A, which can include the Internet, IP multimedia subsystem(IPS) network, and other networks. Generally, the application server 184may be an element offering applications that use IP bearer resourceswith the core network (e.g., UMTS Packet Services (PS) domain, LTE PSdata services, etc.). In this aspect, the P-GW 123 is shown to becommunicatively coupled to an application server 184 via an IP interface125. The application server 184 can also be configured to support one ormore communication services (e.g., Voice-over-Internet Protocol (VoIP)sessions, PTT sessions, group communication sessions, social networkingservices, etc.) for the UEs 101 and 102 via the CN 120.

The P-GW 123 may further be a node for policy enforcement and chargingdata collection. Policy and Charging Rules Function (PCRF) 126 is thepolicy and charging control element of the CN 120. In a non-roamingscenario, in some aspects, there may be a single PCRF in the Home PublicLand Mobile Network (HPLMN) associated with a UEs Internet ProtocolConnectivity Access Network (IP-CAN) session. In a roaming scenario withlocal breakout of traffic, there may be two PCRFs associated with a UE'sIP-CAN session: a Home PCRF (H-PCRF) within a HPLMN and a Visited PCRF(V-PCRF) within a Visited Public Land Mobile Network (VPLMN). The PCRF126 may be communicatively coupled to the application server 184 via theP-GW 123. The application server 184 may signal the PCRF 126 to indicatea new service flow and select the appropriate Quality of Service (QoS)and charging parameters. The PCRF 126 may provision this rule into aPolicy and Charging Enforcement Function (PCEF) (not shown) with theappropriate traffic flow template (TFT) and QoS class of identifier(QCI), which commences the QoS and charging as specified by theapplication server 184.

In an example, any of the nodes 111 or 112 can be configured tocommunicate to the UEs 101, 102 (e.g., dynamically) an antenna panelselection and a receive (Rx) beam selection that can be used by the UEfor data reception on a physical downlink shared channel (PDSCH) as wellas for channel state information reference signal (CSI-RS) measurementsand channel state information (CSI) calculation.

In an example, any of the nodes 111 or 112 can be configured tocommunicate to the UEs 101, 102 (e.g., dynamically) an antenna panelselection and a transmit (Tx) beam selection that can be used by the UEfor data transmission on a physical uplink shared channel (PUSCH) aswell as for sounding reference signal (SRS) transmission.

In some aspects, the UEs 101 and 102 can be configured with percomponent carrier (CC) measurement gap, which can include configuring(e.g. by the nodes 111 or 112) one or more of the following parameters:Nfreq, n, effective Nfreq, r, as defined 3GPP Technical Specification(TS) 36.133.

In some aspects, a UE may reconfigure a receiver bandwidth, carrierfrequency, or turn on/off one or more of its RF chains when performingmeasurements on a primary cell, activated secondary cell, the activatedsecondary cell and/or unused RF chains. The measurements however maycause interruption on a primary cell or activated secondary cell (orboth). In this regard, a UE can be configured with a network controlledsmall gap (NCSG), which can include a network configured measurementgap. For the UE to perform the measurements and avoid interruptions onthe primary cell or the activated secondary cell. More specifically, aUE can stop data transmission during the measurement gap, perform RFretuning to another frequency carrier to perform measurements, and thenretune the RF circuitry back to the original frequency.

In some aspects, the NCSG can be configured per UE (instead of per CC)in instances when, e.g., the UE does not support per CC gapconfiguration. An example use case of NCSG configuration can include aUE which is configured with either non-carrier aggregation or carrieraggregation operation, and has a spare RF chain which can makemeasurements without gap, but those measurements can cause interruptionto the serving cell(s).

In some aspects, per UE NCSG can be supported when the UE does notsupport per CC configuration of a measurement gap for performingmeasurements on one or more frequencies using one or more of the UE RFchains. In this case, the UE can be configured to report whether or notit needs NCSG for one or more cells in a carrier aggregation case, andfor a primary cell for noncarrier aggregation case. In some aspects, thefollowing options can be used to configure per UE NCSG:

Option 1: use an existing legacy benefit from interruption gapsignalling and configuration. In this case, the UE can take an inferiorfrequency measurement and report the measurement based on one bit (i.e.,reporting based on UE's best knowledge).

Option 2: send a bit map of band combinations indicating (e.g., to aneNB) whether the UE needs NCSG or not. In this option, UE capabilityinformation element can be used for the reporting and the size of suchelement can be larger than optimal.

Option 3: reuse existing UE feedback indication and add a capability toseparate support of per CC configuration and support of per CCindication. However, since this is a per UE indication andconfiguration, the UE can indicate whether all serving cell IDs needNCSG or not. In some aspects, misconfiguration can occur when thisoption is used.

In some aspects, additional signaling can be used to support per UE NCSGconfiguration. For example, NCSG configuration information 141A can becommunicated (e.g. from node 111 or 112) to UE 101. The NCSGconfiguration information 141A can be separated into multipletransmissions and can include, e.g., an indication of one or moreinformation elements or messages that the UE can use to request NCSGconfiguration. Additionally, in instances when the UE requests NCSG, theNCSG configuration information 141A can include information used by theUE to configure NCSG measurements on a serving or non-serving frequency(e.g., visible interruption length period duration and measurementlength period duration as well as identification of one or moresubframes constituting a measurement gap where the NCSG measurements canbe performed).

After the NCSG configuration information 141A is received by the UE 101,the NCSG measurements can be performed on the configured frequency andfor the duration of a measurement gap specified by the NCSGconfiguration 140A. The obtained NCSG measurements 142A can becommunicated back to the network for further processing (e.g., todetermine whether or not to perform the handover). Additionalinformation regarding the per UE NCSG configuration is discussed hereinbelow in reference to FIG. 7 to FIG. 12.

FIG. 1B is a simplified diagram of a next generation (NG) systemarchitecture 140B in accordance with some aspects. Referring to FIG. 1B,the NG system architecture 140B includes RAN 110 and a 5G network core(5GC) 120. The NG-RAN 110 can include a plurality of nodes, such as gNBs128 and NG-eNBs 130. The gNBs 128 and the NG-eNBs 130 can becommunicatively coupled to the UE 102 via, e.g., an N1 interface.

The core network 120 (e.g., a 5G core network or 5GC) can include anaccess and mobility management function (AMF) 132 and/or a user planefunction (UPF) 134. The AMF 132 and the UPF 134 can be communicativelycoupled to the gNBs 128 and the NG-eNBs 130 via NG interfaces. Morespecifically, in some aspects, the gNBs 128 and the NG-eNBs 130 can beconnected to the AMF 132 by NG-C interfaces, and to the UPF 134 by NG-Uinterfaces. The gNBs 128 and the NG-eNBs 130 can be coupled to eachother via Xn interfaces.

In some aspects, a gNB 128 can include a node providing new radio (NR)user plane and control plane protocol termination towards the UE, and isconnected via the NG interface to the 5GC 120. In some aspects, anNG-eNB 130 can include a node providing evolved universal terrestrialradio access (E-UTRA) user plane and control plane protocol terminationstowards the UE, and is connected via the NG interface to the 5GC 120.

In some aspects, each of the gNBs 128 and the NG-eNBs 130 can beimplemented as a base station, a mobile edge server, a small cell, ahome eNB, and so forth.

FIG. 1C illustrates an example MulteFire Neutral Host Network (NHN) 5Garchitecture 140C in accordance with some aspects. Referring to FIG. 1C,the MulteFire 5G architecture 140C can include the UE 102, NG-RAN 110,and core network 120. The NG-RAN 110 can be a MulteFire NG-RAN (MFNG-RAN), and the core network 120 can be a MulteFire 5G neutral hostnetwork (NHN).

In some aspects, the MF NHN 120 can include a neutral host AMF (NH AMF)132, a NH SMF 136, a NH UPF 134, and a local AAA proxy 151C. The AAAproxy 151C can provide connection to a 3GPP AAA server 155C and aparticipating service provider AAA (PSP AAA) server 153C. The NH-UPF 134can provide a connection to a data network 157C.

The MF NG-RAN 120 can provide similar functionalities as an NG-RANoperating under a 3GPP specification. The NH-AMF 132 can be configuredto provide similar functionality as a AMF in a 3GPP 5G core network(e.g., as described in reference to FIG. 1D). The NH-SMF 136 can beconfigured to provide similar functionality as a SMF in a 3GPP 5G corenetwork (e.g., as described in reference to FIG. 1D). The NH-UPF 134 canbe configured to provide similar functionality as a UPF in a 3GPP 5Gcore network (e.g., as described in reference to FIG. 1D).

FIG. 1D illustrates a functional split between NG-RAN and the 5G Core(5GC) in accordance with some aspects. Referring to FIG. 1D, there isillustrated a more detailed diagram of the functionalities that can beperformed by the gNBs 128 and the NG-eNBs 130 within the NG-RAN 110, aswell as the AMF 132, the UPF 134, and the SMF 136 within the 5GC 120. Insome aspects, the 5GC 120 can provide access to the Internet 138 to oneor more devices via the NG-RAN 110.

In some aspects, the gNBs 128 and the NG-eNBs 130 can be configured tohost the following functions: functions for Radio Resource Management(e.g., inter-cell radio resource management 129A, radio bearer control129B, connection mobility control 129C, radio admission control 129D,dynamic allocation of resources to UEs in both uplink and downlink(scheduling) 129F); IP header compression, encryption and integrityprotection of data; selection of an AMF at UE attachment when no routingto an AMF can be determined from the information provided by the UE;routing of User Plane data towards UPF(s); routing of Control Planeinformation towards AMF; connection setup and release; scheduling andtransmission of paging messages (originated from the AMF); schedulingand transmission of system broadcast information (originated from theAMF or Operation and Maintenance); measurement and measurement reportingconfiguration for mobility and scheduling 129E; transport level packetmarking in the uplink; session management; support of network slicingQoS flow management and mapping to data radio bearers; support of UEs inRRC_INACTIVE state; distribution function for non-access stratum (NAS)messages; radio access network sharing dual connectivity; and tightinterworking between NR and E-UTRA, to name a few.

In some aspects, the AMF 132 can be configured to host the followingfunctions, for example: NAS signaling termination; NAS signalingsecurity 133A; access stratum (AS) security control; inter core network(CN) node signaling for mobility between 3GPP access networks; idlestate/mode mobility handling 133B, including mobile device, such as a UEreachability (e.g., control and execution of paging retransmission);registration area management; support of intra-system and inter-systemmobility; access authentication; access authorization including check ofroaming rights; mobility management control (subscription and policies);support of network slicing and/or SM F selection, among other functions.

The UPF 134 can be configured to host the following functions, forexample: mobility anchoring 135A (e.g., anchor point forIntra-/Inter-RAT mobility); packet data unit (PDU) handling 135B (e.g.,external PDU session point of interconnect to data network); packetrouting and forwarding packet inspection and user plane part of policyrule enforcement; traffic usage reporting uplink classifier to supportrouting traffic flows to a data network; branching point to supportmulti-homed PDU session; QoS handling for user plane, e.g., packetfiltering gating UL/DL rate enforcement; uplink traffic verification(SDF to QoS flow mapping); and/or downlink packet buffering and downlinkdata notification triggering among other functions.

The Session Management function (SMF) 136 can be configured to host thefollowing functions, for example: session management; UE IP addressallocation and management 137A; selection and control of user planefunction (UPF); PDU session control 137B, including configuring trafficsteering at UPF 134 to route traffic to proper destination; control partof policy enforcement and QoS; and/or downlink data notification, amongother functions.

FIG. 1E and FIG. 1F illustrate a non-roaming 5G system architecture inaccordance with some aspects. Referring to FIG. 1E, there is illustrateda 5G system architecture 140E in a reference point representation. Morespecifically, UE 102 can be in communication with RAN 110 as well as oneor more other 5G core (5GC) network entities. The 5G system architecture140E includes a plurality of network functions (NFs), such as access andmobility management function (AMF) 132, session management function(SMF) 136, policy control function (PCF) 148, application function (AF)150, user plane function (UPF) 134, network slice selection function(NSSF) 142, authentication server function (AUSF) 144, and unified datamanagement (UDM)/home subscriber server (HSS) 146. The UPF 134 canprovide a connection to a data network (DN) 152, which can include, forexample, operator services, Internet access, or third-party services.The AMF can be used to manage access control and mobility, and can alsoinclude network slice selection functionality. The SM F can beconfigured to set up and manage various sessions according to a networkpolicy. The UPF can be deployed in one or more configurations accordingto a desired service type. The PCF can be configured to provide a policyframework using network slicing mobility management, and roaming(similar to PCRF in a 4G communication system). The UDM can beconfigured to store subscriber profiles and data (similar to an HSS in a4G communication system).

In some aspects, the 5G system architecture 140E includes an IPmultimedia subsystem (IMS) 168E as well as a plurality of IP multimediacore network subsystem entities, such as call session control functions(CSCFs). More specifically, the IMS 168E includes a CSCF, which can actas a proxy CSCF (P-CSCF) 162E, a serving CSCF (S-CSCF) 164E, anemergency CSCF (E-CSCF) (not illustrated in FIG. 1E), and/orinterrogating CSCF (I-CSCF) 166E. The P-CSCF 162E can be configured tobe the first contact point for the UE 102 within the IM subsystem (IMS)168E. The S-CSCF 164E can be configured to handle the session states inthe network, and the E-CSCF can be configured to handle certain aspectsof emergency sessions such as routing an emergency request to thecorrect emergency center or PSAP. The I-CSCF 166E can be configured tofunction as the contact point within an operator's network for all IMSconnections destined to a subscriber of that network operator, or aroaming subscriber currently located within that network operator'sservice area. In some aspects, the I-CSCF 166E can be connected toanother IP multimedia network 170E, e.g. an IMS operated by a differentnetwork operator.

In some aspects, the UDM/HSS 146 can be coupled to an application server160E, which can include a telephony application server (TAS) or anotherapplication server (AS). The AS 160E can be coupled to the IMS 168E viathe S-CSCF 164E and/or the I-CSCF 166E.

In some aspects, the 5G system architecture 140E can use a unifiedaccess barring mechanism using one or more of the techniques describedherein, which access barring mechanism can be applicable for all RRCstates of the UE 102, such as RRC_IDLE, RRC_CONNECTED, and RRC_INACTIVEstates.

In some aspects, the 5G system architecture 140E can be configured touse 5G access control mechanism techniques described herein, based onaccess categories that can be categorized by a minimum default set ofaccess categories, which are common across all networks. Thisfunctionality can allow the public land mobile network PLMN, such as avisited PLMN (VPLMN) to protect the network against different types ofregistration attempts, enable acceptable service for the roamingsubscriber and enable the VPLMN to control access attempts aiming atreceiving certain basic services. It also provides more options andflexibility to individual operators by providing a set of accesscategories, which can be configured and used in operator specific ways.

Referring to FIG. 1F, there is illustrated a 5G system architecture 140Fand a service-based representation. System architecture 140F can besubstantially similar to (or the same as) system architecture 140E. Inaddition to the network entities illustrated in FIG. 1E, systemarchitecture 140F can also include a network exposure function (NEF) 154and a network repository function (NRF) 156.

In some aspects, 5G system architectures can be service-based andinteraction between network functions can be represented bycorresponding point-to-point reference points N1 (as illustrated in FIG.1E) or as service-based interfaces (as illustrated in FIG. 1F).

A reference point representation shows that an interaction can existbetween corresponding NF services. For example, FIG. 1E illustrates thefollowing reference points: N1 (between the UE 102 and the AMF 132), N2(between the RAN 110 and the AMF 132), N3 (between the RAN 110 and theUPF 134), N4 (between the SMF 136 and the UPF 134), N5 (between the PCF148 and the AF 150), N6 (between the UPF 134 and the DN 152), N7(between the SMF 136 and the PCF 148), N8 (between the UDM 146 and theAMF 132), N9 (between two UPFs 134), N10 (between the UDM 146 and theSMF 136), N11 (between the AMF 132 and the SMF 136), N12 (between theAUSF 144 and the AMF 132), N13 (between the AUSF 144 and the UDM 146),N14 (between two AMFs 132), N15 (between the PCF 148 and the AMF 132 incase of a non-roaming scenario, or between the PCF 148 and a visitednetwork and AMF 132 in case of a roaming scenario), N16 (between twoSMFs; not illustrated in FIG. 1E), and N22 (between AMF 132 and NSSF142). Other reference point representations not shown in FIG. 1E canalso be used.

In some aspects, as illustrated in FIG. 1F, service-basedrepresentations can be used to represent network functions within thecontrol plane that enable other authorized network functions to accesstheir services. In this regard, 5G system architecture 140F can includethe following service-based interfaces: Namf 158H (a service-basedinterface exhibited by the AMF 132), Nsmf 158I (a service-basedinterface exhibited by the SMF 136), Nnef 158B (a service-basedinterface exhibited by the NEF 154), Npcf 158D (a service-basedinterface exhibited by the PCF 148), a Nudm 158E (a service-basedinterface exhibited by the UDM 146), Naf 158F (a service-based interfaceexhibited by the AF 150), Nnrf 158C (a service-based interface exhibitedby the NRF 156), Nnssf 158A (a service-based interface exhibited by theNSSF 142), Nausf 158G (a service-based interface exhibited by the AUSF144). Other service-based interfaces (e.g., Nudr, N5g-eir, and Nudsf)not shown in FIG. 1F can also be used.

FIG. 1G illustrates an example CIoT network architecture in accordancewith some aspects. Referring to FIG. 1G, the CIoT architecture 140G caninclude the UE 102 and the RAN 110 coupled to a plurality of corenetwork entities. In some aspects, the UE 102 can be machine-typecommunication (MTC) UE. The CIoT network architecture 140G can furtherinclude a mobile services switching center (MSC) 160, MME 121, a servingGPRS support note (SGSN) 162, a S-GW 122, an IP-Short-Message-Gateway(IP-SM-GW) 164, a Short Message Service Service Center (SMS-SC)/gatewaymobile service center (GMSC)/Interworking MSC (IWMSC) 166, MTCinterworking function (MTC-IWF) 170, a Service Capability ExposureFunction (SCEF) 172, a gateway GPRS support node (GGSN)/Packet-GW (P-GW)174, a charging data function (CDF)/charging gateway function (CGF) 176,a home subscriber server (HSS)/a home location register (HLR) 177, shortmessage entities (SME) 168, MTC authorization, authentication, andaccounting (MTC AAA) server 178, a service capability server (SCS) 180,and application servers (AS) 182 and 184.

In some aspects, the SCEF 172 can be configured to securely exposeservices and capabilities provided by various 3GPP network interfaces.The SCEF 172 can also provide means for the discovery of the exposedservices and capabilities, as well as access to network capabilitiesthrough various network application programming interfaces (e.g., APIinterfaces to the SCS 180).

FIG. 1G further illustrates various reference points between differentservers, functions, or communication nodes of the CIoT networkarchitecture 140G. Some example reference points related to MTC-IWF 170and SCEF 172 include the following Tsms (a reference point used by anentity outside the 3GPP network to communicate with UEs used for MTC viaSMS), Tsp (a reference point used by a SCS to communicate with theMTC-IWF related control plane signaling), T4 (a reference point usedbetween MTC-IWF 170 and the SMS-SC 166 in the HPLMN), T6a (a referencepoint used between SCEF 172 and serving MME 121), T6b (a reference pointused between SCEF 172 and serving SGSN 162), T8 (a reference point usedbetween the SCEF 172 and the SCS/AS 180/182), S6m (a reference pointused by MTC-IWF 170 to interrogate HSS/HLR 177), S6n (a reference pointused by MTC-AAA server 178 to interrogate HSS/HLR 177), and S6t (areference point used between SCEF 172 and HSS/HLR 177).

In some aspects, the CIoT UE 102 can be configured to communicate withone or more entities within the CIoT architecture 140G via the RAN 110according to a Non-Access Stratum (NAS) protocol, and using one or morereference points, such as a narrowband air interface, for example, basedon one or more communication technologies, such as OrthogonalFrequency-Division Multiplexing (OFDM) technology. As used herein, theterm “CIoT UE” refers to a UE capable of CIoT optimizations, as part ofa CIoT communications architecture.

In some aspects, the NAS protocol can support a set of NAS messages forcommunication between the CIoT UE 102 and an Evolved Packet System (EPS)Mobile Management Entity (MME) 121 and SGSN 162.

In some aspects, the CIoT network architecture 140F can include a packetdata network, an operator network, or a cloud service network, havingfor example, among other thing, a Service Capability Server (SCS) 180,an Application Server (AS) 182, or one or more other external servers ornetwork components.

The RAN 110 can be coupled to the HSS/HLR servers 177 and the AAAservers 178 using one or more reference points including for example, anair interface based on an S6a reference point, and configured toauthenticate/authorize CIoT UE 102 to access the CIoT network. The RAN110 can be coupled to the CIoT network architecture 140G using one ormore other reference points including for example, an air interfacecorresponding to an SGi/Gi interface for 3GPP accesses. The RAN 110 canbe coupled to the SCEF 172 using for example, an air interface based ona T6a/T6b reference point, for service capability exposure. In someaspects, the SCEF 172 may act as an API GW towards a third-partyapplication server such as AS 182. The SCEF 172 can be coupled to theHSS/HLR 177 and MTC AAA 178 servers using an S6t reference point, andcan further expose an Application Programming Interface to networkcapabilities.

In certain examples, one or more of the CIoT devices disclosed herein,such as the CIoT UE 102, the CIoT RAN 110, etc., can include one or moreother non-CIoT devices, or non-CIoT devices acting as CIoT devices, orhaving functions of a CIoT device. For example, the CIoT UE 102 caninclude a smart phone, a tablet computer, or one or more otherelectronic device acting as a CIoT device for a specific function, whilehaving other additional functionality.

In some aspects, the RAN 110 can include a CIoT enhanced Node B (CIoTeNB) 111 communicatively coupled to the CIoT Access Network Gateway(CIoT GW) 195. In certain examples, the RAN 110 can include multiplebase stations (e.g., CIoT eNBs) connected to the CIoT GW 195, which caninclude MSC 160, MME 121, SGSN 162, and/or S-GW 122. In certainexamples, the internal architecture of RAN 110 and CIoT GW 195 may beleft to the implementation and need not be standardized.

As used herein, the term “circuitry” may refer to, be part of, orinclude an Application Specific Integrated Circuit (ASIC) or otherspecial purpose circuit, an electronic circuit, a processor (shared,dedicated, or group), or memory (shared, dedicated, or group) executingone or more software or firmware programs, a combinational logiccircuit, or other suitable hardware components that provide thedescribed functionality. In some aspects, the circuitry may beimplemented in, or functions associated with the circuitry may beimplemented by, one or more software or firmware modules. In someaspects, circuitry may include logic, at least partially operable inhardware. In some aspects, circuitry as well as modules disclosed hereinmay be implemented in combinations of hardware, software and/orfirmware. In some aspects, functionality associated with a circuitry canbe distributed across more than one piece of hardware orsoftware/firmware module. In some aspects, modules (as disclosed herein)may include logic, at least partially operable in hardware. Aspectsdescribed herein may be implemented into a system using any suitablyconfigured hardware or software.

FIG. 1H illustrates an example Service Capability Exposure Function(SCEF) in accordance with some aspects. Referring to FIG. 1H, the SCEF172 can be configured to expose services and capabilities provided by3GPP network interfaces to external third party service provider servershosting various applications. In some aspects, a 3GPP network such asthe CIoT architecture 140G, can expose the following services andcapabilities: a home subscriber server (HSS) 116H, a policy and chargingrules function (PCRF) 118H, a packet flow description function (PFDF)120H, a MME/SGSN 122H, a broadcast multicast service center (BM-SC)124H, a serving call server control function (S-CSCF) 126H, a RANcongestion awareness function (RCAF) 128H, and one or more other networkentities 130H. The above-mentioned services and capabilities of a 3GPPnetwork can communicate with the SCEF 172 via one or more interfaces asillustrated in FIG. 1H.

The SCEF 172 can be configured to expose the 3GPP network services andcapabilities to one or more applications running on one or more servicecapability server (SCS)/application server (AS), such as SCS/AS 102H,104H, . . . , 106H. Each of the SCS/AG 102H-106H can communicate withthe SCEF 172 via application programming interfaces (APIs) 108H, 110H,112H, . . . , 114H, as seen in FIG. 1H.

FIG. 1I illustrates an example roaming architecture for SCEF inaccordance with some aspects. Referring to FIG. 1I, the SCEF 172 can belocated in HPLMN 1101 and can be configured to expose 3GPP networkservices and capabilities, such as 102I, . . . , 104I. In some aspects,3GPP network services and capabilities, such as 106I, . . . , 108I, canbe located within VPLMN 112I. In this case, the 3GPP network servicesand capabilities within the VPLMN 112I can be exposed to the SCEF 172via an interworking SCEF (IWK-SCEF) 197 within the VPLMN 112I.

FIG. 2 illustrates example components of a device 200 in accordance withsome aspects. In some aspects, the device 200 may include applicationcircuitry 202, baseband circuitry 204, Radio Frequency (RF) circuitry206, front-end module (FEM) circuitry 208, one or more antennas 210, andpower management circuitry (PMC) 212 coupled together at least as shown.The components of the illustrated device 200 may be included in a UE ora RAN node. In some aspects, the device 200 may include fewer elements(e.g., a RAN node may not utilize application circuitry 202, and insteadinclude a processor/controller to process IP data received from an EPC).In some aspects, the device 200 may include additional elements such as,for example, memory/storage, display, camera, sensor, and/orinput/output (I/O) interface elements. In other aspects, the componentsdescribed below may be included in more than one device (e.g., saidcircuitries may be separately included in more than one device forCloud-RAN (C-RAN) implementations).

The application circuitry 202 may include one or more applicationprocessors. For example, the application circuitry 202 may includecircuitry such as, but not limited to, one or more single-core ormulti-core processors. The processor(s) may include any combination ofgeneral-purpose processors, special-purpose processors, and dedicatedprocessors (e.g., graphics processors, application processors, etc.).The processors may be coupled with, and/or may include, memory/storageand may be configured to execute instructions stored in thememory/storage to enable various applications or operating systems torun on the device 200. In some aspects, processors of applicationcircuitry 202 may process IP data packets received from an EPC.

The baseband circuitry 204 may include circuitry such as, but notlimited to, one or more single-core or multi-core processors. Thebaseband circuitry 204 may include one or more baseband processors orcontrol logic to process baseband signals received from a receive signalpath of the RF circuitry 206 and to generate baseband signals for atransmit signal path of the RF circuitry 206. Baseband processingcircuitry 204 may interface with the application circuitry 202 forgeneration and processing of the baseband signals and for controllingoperations of the RF circuitry 206. For example, in some aspects, thebaseband circuitry 204 may include a third generation (3G) basebandprocessor 204A, a fourth generation (4G) baseband processor 204B, afifth generation (5G) baseband processor 204C, or other basebandprocessor(s) 204D for other existing generations, generations indevelopment or to be developed in the future (e.g., second generation(2G), sixth generation (6G), etc.). The baseband circuitry 204 (e.g.,one or more of baseband processors 204A-D) may handle various radiocontrol functions that enable communication with one or more radionetworks via the RF circuitry 206. In other aspects, some or all of thefunctionality of baseband processors 204A-D may be included in modulesstored in the memory 204G and executed via a Central Processing Unit(CPU) 204E. The radio control functions may include, but are not limitedto, signal modulation/demodulation, encoding/decoding radio frequencyshifting etc. In some aspects, modulation/demodulation circuitry of thebaseband circuitry 204 may include Fast-Fourier Transform (FFT),precoding or constellation mapping/de-mapping functionality. In someaspects, encoding/decoding circuitry of the baseband circuitry 204 mayinclude convolution, tail-biting convolution, turbo, Viterbi, orLow-Density Parity Check (LDPC) encoder/decoder functionality. Aspectsof modulation/demodulation and encoder/decoder functionality are notlimited to these examples and may include other suitable functionalityin other aspects.

In some aspects, the baseband circuitry 204 may include one or moreaudio digital signal processor(s) (DSP) 204F. The audio DSP(s) 204F maybe include elements for compression/decompression and echo cancellationand may include other suitable processing elements in other aspects.Components of the baseband circuitry 204 may be suitably combined in asingle chip, a single chipset, or disposed on a same circuit board insome aspects. In some aspects, some or all of the constituent componentsof the baseband circuitry 204 and the application circuitry 202 may beimplemented together such as, for example, on a system on a chip (SOC).

In some aspects, the baseband circuitry 204 may provide forcommunication compatible with one or more radio technologies. Forexample, in some aspects, the baseband circuitry 204 may supportcommunication with an evolved universal terrestrial radio access network(EUTRAN) or other wireless metropolitan area networks (WMAN), a wirelesslocal area network (WLAN), and/or a wireless personal area network(WPAN). Baseband circuitry 204 configured to support radiocommunications of more than one wireless protocol may be referred to asmulti-mode baseband circuitry, in some aspects.

RF circuitry 206 may enable communication with wireless networks usingmodulated electromagnetic radiation through a non-solid medium. Invarious aspects, the RF circuitry 206 may include switches, filters,amplifiers, etc. to facilitate the communication with the wirelessnetwork. RF circuitry 206 may include a receive signal path which mayinclude circuitry to down-convert RF signals received from the FEMcircuitry 208 and provide baseband signals to the baseband circuitry204. RF circuitry 206 may also include a transmit signal path which mayinclude circuitry to up-convert baseband signals provided by thebaseband circuitry 204 and provide RF output signals to the FEMcircuitry 208 for transmission.

In some aspects, the receive signal path of the RF circuitry 206 mayinclude a mixer 206A, an amplifier 206B, and a filter 206C. In someaspects, the transmit signal path of the RF circuitry 206 may include afilter 206C and a mixer 206A. RF circuitry 206 may also include asynthesizer 206D for synthesizing a frequency for use by the mixer 206Aof the receive signal path and the transmit signal path. In someaspects, the mixer 206A of the receive signal path may be configured todown-convert RF signals received from the FEM circuitry 208 based on thesynthesized frequency provided by synthesizer 206D. The amplifier 206Bmay be configured to amplify the down-converted signals and the filter206C may be a low-pass filter (LPF) or band-pass filter (BPF) configuredto remove unwanted signals from the down-converted signals to generateoutput baseband signals. Output baseband signals may be provided to thebaseband circuitry 204 for further processing In some aspects, theoutput baseband signals may optionally be zero-frequency basebandsignals. In some aspects, mixer 206A of the receive signal path maycomprise passive mixers.

In some aspects, the mixer 206A of the transmit signal path may beconfigured to up-convert input baseband signals based on the synthesizedfrequency provided by the synthesizer 206D to generate RF output signalsfor the FEM circuitry 208. The baseband signals may be provided by thebaseband circuitry 204 and may be filtered by filter 206C.

In some aspects, the mixer 206A of the receive signal path and the mixer206A of the transmit signal path may include two or more mixers and maybe arranged for quadrature down conversion and up conversion,respectively. In some aspects, the mixer 206A of the receive signal pathand the mixer 206A of the transmit signal path may include two or moremixers and may be arranged for image rejection (e.g., Hartley imagerejection). In some aspects, the mixer 206A of the receive signal pathand the mixer 206A may be arranged for direct down conversion and directup conversion, respectively. In some aspects, the mixer 206A of thereceive signal path and the mixer 206A of the transmit signal path maybe configured for super-heterodyne operation.

In some aspects, the output baseband signals and the input basebandsignals may optionally be analog baseband signals. According to somealternate aspects, the output baseband signals and the input basebandsignals may be digital baseband signals. In these alternate aspects, theRF circuitry 206 may include analog-to-digital converter (ADC) anddigital-to-analog converter (DAC) circuitry and the baseband circuitry204 may include a digital baseband interface to communicate with the RFcircuitry 206.

In some dual-mode aspects, a separate radio IC circuitry may optionallybe provided for processing signals for each spectrum.

In some aspects, the synthesizer 206D may optionally be a fractional-Nsynthesizer or a fractional N/N+1 synthesizer, although other types offrequency synthesizers may be suitable. For example, the synthesizer206D may be a delta-sigma synthesizer, a frequency multiplier, or asynthesizer comprising a phase-locked loop with a frequency divider.

The synthesizer 206D may be configured to synthesize an output frequencyfor use by the mixer 206A of the RF circuitry 206 based on a frequencyinput and a divider control input. In some aspects, the synthesizer 206Dmay be a fractional N/N+1 synthesizer.

In some aspects, frequency input may be provided by a voltage controlledoscillator (VCO), although that is not a requirement. Divider controlinput may be provided, for example, by either the baseband circuitry 204or the applications circuitry 202 depending on the desired outputfrequency. In some aspects, a divider control input (e.g., N) may bedetermined from a look-up table based on a channel indicated by theapplications circuitry 202.

Synthesizer circuitry 206D of the RF circuitry 206 may include adivider, a delay-locked loop (DLL), a multiplexer and a phaseaccumulator. In some aspects, the divider may be a dual modulus divider(DMD) and the phase accumulator may be a digital phase accumulator(DPA). In some aspects, the DMD may be configured to divide the inputsignal by either N or N+1 (e.g., based on a carry out) to provide afractional division ratio. In some example aspects, the DLL may includea set of cascaded, tunable, delay elements, a phase detector, a chargepump and a D-type flip-flop. In these aspects, the delay elements may beconfigured to break a VCO period up into Nd equal packets of phase,where Nd is the number of delay elements in the delay line. In this way,the DLL provides negative feedback to assist in keeping the total delaythrough the delay line to one VCO cycle.

In some aspects, synthesizer circuitry 206D may be configured togenerate a carrier frequency as the output frequency, while in otheraspects, the output frequency may be a multiple of the carrier frequency(e.g., twice the carrier frequency, or four times the carrier frequency)and may be used in conjunction with quadrature generator and dividercircuitry to generate multiple signals at the carrier frequency withmultiple different phases with respect to each other. In some aspects,the output frequency may be a LO frequency (fLO). In some aspects, theRF circuitry 206 may include an IQ/polar converter.

FEM circuitry 208 may include a receive signal path which may includecircuitry configured to operate on RF signals received from one or moreantennas 210, and/or to amplify the received signals and provide theamplified versions of the received signals to the RF circuitry 206 forfurther processing FEM circuitry 208 may also include a transmit signalpath which may include circuitry configured to amplify signals fortransmission provided by the RF circuitry 206 for transmission by one ormore of the one or more antennas 210. In various aspects, theamplification through the transmit signal paths or the receive signalpaths may be done in part or solely in the RF circuitry 206, in part orsolely in the FEM circuitry 208, or in both the RF circuitry 206 and theFEM circuitry 208.

In some aspects, the FEM circuitry 208 may include a TX/RX switch toswitch between transmit mode and receive mode operation. The FEMcircuitry 208 may include a receive signal path and a transmit signalpath. The receive signal path of the FEM circuitry 208 may include anLNA to amplify received RF signals and provide the amplified received RFsignals as an output (e.g., to the RF circuitry 206). The transmitsignal path of the FEM circuitry 208 may include a power amplifier (PA)to amplify input RF signals (e.g., provided by RF circuitry 206), andone or more filters to generate RF signals for subsequent transmission(e.g., by one or more of the one or more antennas 210).

In some aspects, the PMC 212 may manage power provided to the basebandcircuitry 204. The PMC 212 may control power-source selection, voltagescaling battery charging and/or DC-to-DC conversion. The PMC 212 may, insome aspects, be included when the device 200 is capable of beingpowered by a battery, for example, when the device is included in a UE.The PMC 212 may increase the power conversion efficiency while providingbeneficial implementation size and heat dissipation characteristics.

FIG. 2 shows the PMC 212 coupled with the baseband circuitry 204. Inother aspects, the PMC 212 may be additionally or alternatively coupledwith, and perform similar power management operations for, othercomponents such as, but not limited to, application circuitry 202, RFcircuitry 206, or FEM circuitry 208.

In some aspects, the PMC 212 may control, or otherwise be part of,various power saving mechanisms of the device 200. For example, if thedevice 200 is in an RRC_Connected state, in which it is still connectedto the RAN node as it expects to receive traffic shortly, then it mayenter a state known as Discontinuous Reception Mode (DRX) after a periodof inactivity. During this state, the device 200 may power down forbrief intervals of time and thus save power.

According to some aspects, if there is no data traffic activity for anextended period of time, then the device 200 may transition off to anRRC_Idle state, in which it disconnects from the network and does notperform operations such as channel quality feedback, handover, etc. Thedevice 200 goes into a very low power state and it performs pagingduring which it periodically wakes up to listen to the network and thenpowers down again. The device 200 may transition back to RRC_Connectedstate to receive data.

An additional power saving mode may allow a device to be unavailable tothe network for periods longer than a paging interval (ranging fromseconds to a few hours). During this time, the device 200 in someaspects may be unreachable to the network and may power down. Any datasent during this time incurs a delay, which may be large, and it isassumed the delay is acceptable.

Processors of the application circuitry 202 and processors of thebaseband circuitry 204 may be used to execute elements of one or moreinstances of a protocol stack. For example, processors of the basebandcircuitry 204, alone or in combination, may be used execute Layer 3,Layer 2, or Layer 1 functionality, while processors of the applicationcircuitry 202 may utilize data (e.g., packet data) received from theselayers and further execute Layer 4 functionality (e.g., transmissioncommunication protocol (TCP) and user datagram protocol (UDP) layers).As referred to herein, Layer 3 may comprise a radio resource control(RRC) layer, described in further detail below. As referred to herein,Layer 2 may comprise a medium access control (MAC) layer, a radio linkcontrol (RLC) layer, and a packet data convergence protocol (PDCP)layer, described in further detail below. As referred to herein, Layer 1may comprise a physical (PHY) layer of a UE/RAN node, described infurther detail below.

FIG. 3 illustrates example interfaces of baseband circuitry 204, inaccordance with some aspects. As discussed above, the baseband circuitry204 of FIG. 2 may comprise processors 204A-204E and a memory 204Gutilized by said processors. Each of the processors 204A-204E mayinclude a memory interface, 304A-304E, respectively, to send/receivedata to/from the memory 204G.

The baseband circuitry 204 may further include one or more interfaces tocommunicatively couple to other circuitries/devices, such as a memoryinterface 312 (e.g., an interface to send/receive data to/from memoryexternal to the baseband circuitry 204), an application circuitryinterface 314 (e.g., an interface to send/receive data to/from theapplication circuitry 202 of FIG. 2), an RF circuitry interface 316(e.g., an interface to send/receive data to/from RF circuitry 206 ofFIG. 2), a wireless hardware connectivity interface 318 (e.g., aninterface to send/receive data to/from Near Field Communication (NFC)components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi®components, and other communication components), and a power managementinterface 320 (e.g., an interface to send/receive power or controlsignals to/from the PMC 212).

FIG. 4 is an illustration of a control plane protocol stack inaccordance with some aspects. In one aspect, a control plane 400 isshown as a communications protocol stack between the UE 102, the RANnode 128 (or alternatively, the RAN node 130), and the AMF 132.

The PHY layer 401 may in some aspects transmit or receive informationused by the MAC layer 402 over one or more air interfaces. The PHY layer401 may further perform link adaptation or adaptive modulation andcoding (AMC), power control, cell search (e.g., for initialsynchronization and handover purposes), and other measurements used byhigher layers, such as the RRC layer 405. The PHY layer 401 may in someaspects still further perform error detection on the transport channels,forward error correction (FEC) coding/decoding of the transportchannels, modulation/demodulation of physical channels, interleavingrate matching map ping onto physical channels, and Multiple InputMultiple Output (MIMO) antenna processing.

The MAC layer 402 may in some aspects perform mapping between logicalchannels and transport channels, multiplexing of MAC service data units(SDUs) from one or more logical channels onto transport blocks (TB) tobe delivered to PHY via transport channels, de-multiplexing MAC SDUs toone or more logical channels from transport blocks (TB) delivered fromthe PHY via transport channels, multiplexing MAC SDUs onto TBs,scheduling information reporting error correction through hybridautomatic repeat request (HARQ), and logical channel prioritization.

The RLC layer 403 may in some aspects operate in a plurality of modes ofoperation, including Transparent Mode (TM), Unacknowledged Mode (UM),and Acknowledged Mode (AM). The RLC layer 403 may execute transfer ofupper layer protocol data units (PDUs), error correction throughautomatic repeat request (ARQ) for AM data transfers, and segmentationand reassembly of RLC SDUs for UM and AM data transfers. The RLC layer403 may also maintain sequence numbers independent of the ones in PDCPfor UM and AM data transfers. The RLC layer 403 may also in some aspectsexecute re-segmentation of RLC data PDUs for AM data transfers, detectduplicate data for AM data transfers, discard RLC SDUs for UM and AMdata transfers, detect protocol errors for AM data transfers, andperform RLC re-establishment.

The PDCP layer 404 may in some aspects execute header compression anddecompression of IP data, maintain PDCP Sequence Numbers (SNs), performin-sequence delivery of upper layer PDUs at re-establishment of lowerlayers, perform reordering and eliminate duplicates of lower layer SDUs,execute PDCP PDU routing for the case of split bearers, executeretransmission of lower layer SDUs, cipher and decipher control planeand user plane data, perform integrity protection and integrityverification of control plane and user plane data, control timer-baseddiscard of data, and perform security operations (e.g., cipheringdeciphering integrity protection, integrity verification, etc.).

In some aspects, primary services and functions of the RRC layer 405 mayinclude broadcast of system information (e.g., included in MasterInformation Blocks (MIBs) or System Information Blocks (SIBs) related tothe non-access stratum (NAS)); broadcast of system information relatedto the access stratum (AS); paging initiated by 5GC 120 or NG-RAN 110,establishment, maintenance, and release of an RRC connection between theUE and NG-RAN (e.g., RRC connection paging RRC connection establishment,RRC connection addition, RRC connection modification, and RRC connectionrelease, also for carrier aggregation and Dual Connectivity in NR orbetween E-UTRA and NR); establishment, configuration, maintenance, andrelease of Signalling Radio Bearers (SRBs) and Data Radio Bearers(DRBs); security functions including key management, mobility functionsincluding handover and context transfer, UE cell selection andreselection and control of cell selection and reselection, andinter-radio access technology (RAT) mobility; and measurementconfiguration for UE measurement reporting Said MIBs and SIBs maycomprise one or more information elements (IEs), which may each compriseindividual data fields or data structures. The RRC layer 405 may also,in some aspects, execute QoS management functions, detection of andrecovery from radio link failure, and NAS message transfer between theNAS 406 in the UE and the NAS 406 in the AMF 132.

In some aspects, the following NAS messages can be communicated duringthe corresponding NAS procedure, as illustrated in Table 1 below:

TABLE 1 5G NAS 5G NAS 4G NAS 4G NAS Message Procedure Message nameProcedure Registration Initial Attach Request Attach Requestregistration procedure procedure Registration Mobility Tracking AreaTracking area Request registration Update (TAU) updating update Requestprocedure procedure Registration Periodic TAU Request Periodic Requestregistration tracking area update updating procedure procedureDeregistration Deregistration Detach Detach Request procedure Requestprocedure Service Service request Service Service request Requestprocedure Request or procedure Extended Service Request PDU Session PDUsession PDN PDN Establishment establishment Connectivity connectivityRequest procedure Request procedure

In some aspects, when the same message is used for more than oneprocedure, then a parameter can be used (e.g., registration type or TAUtype) which indicates the specific purpose of the procedure, e.g.registration type=“initial registration”, “mobility registration update”or “periodic registration update”.

The UE 101 and the RAN node 128/130 may utilize an NG radio interface(e.g., an LTE-Uu interface or an NR radio interface) to exchange controlplane data via a protocol stack comprising the PHY layer 401, the MAClayer 402, the RLC layer 403, the PDCP layer 404, and the RRC layer 405.

The non-access stratum (NAS) protocols 406 form the highest stratum ofthe control plane between the UE 101 and the AMF 132 as illustrated inFIG. 4. In aspects, the NAS protocols 406 support the mobility of the UE101 and the session management procedures to establish and maintain IPconnectivity between the UE 101 and the UPF 134. In some aspects, the UEprotocol stack can include one or more upper layers, above the NAS layer406. For example, the upper layers can include an operating system layer424, a connection manager 420, and application layer 422. In someaspects, the application layer 422 can include one or more clients whichcan be used to perform various application functionalities, includingproviding an interface for and communicating with one or more outsidenetworks. In some aspects, the application layer 422 can include an IPmultimedia subsystem (IMS) client 426.

The NG Application Protocol (NG-AP) layer 415 may support the functionsof the N2 and N3 interface and comprise Elementary Procedures (EPs). AnEP is a unit of interaction between the RAN node 128/130 and the 5GC120. In certain aspects, the NG-AP layer 415 services may comprise twogroups: UE-associated services and non UE-associated services. Theseservices perform functions including but not limited to: UE contextmanagement, PDU session management and management of correspondingNG-RAN resources (e.g. Data Radio Bearers [DRBs]), UE capabilityindication, mobility, NAS signaling transport, and configurationtransfer (e.g. for the transfer of SON information).

The Stream Control Transmission Protocol (SCTP) layer (which mayalternatively be referred to as the SCTP/IP layer) 414 may ensurereliable delivery of signaling messages between the RAN node 128/130 andthe AMF 132 based, in part, on the IP protocol, supported by the IPlayer 413. The L2 layer 412 and the L1 layer 411 may refer tocommunication links (e.g., wired or wireless) used by the RAN node128/130 and the AMF 132 to exchange information.

The RAN node 128/130 and the AMF 132 may utilize an N2 interface toexchange control plane data via a protocol stack comprising the L1 layer411, the L2 layer 412, the IP layer 413, the SCTP layer 414, and theS1-AP layer 415.

FIG. 5 is an illustration of a user plane protocol stack in accordancewith some aspects. In this aspect, a user plane 500 is shown as acommunications protocol stack between the UE 102, the RAN node 128 (oralternatively, the RAN node 130), and the UPF 134. The user plane 500may utilize at least some of the same protocol layers as the controlplane 400. For example, the UE 102 and the RAN node 128 may utilize anNR radio interface to exchange user plane data via a protocol stackcomprising the PHY layer 401, the MAC layer 402, the RLC layer 403, thePDCP layer 404, and the Service Data Adaptation Protocol (SDAP) layer416. The SDAP layer 416 may, in some aspects, execute a mapping betweena Quality of Service (QoS) flow and a data radio bearer (DRB) and amarking of both DL and UL packets with a QoS flow ID (QFI). In someaspects, an IP protocol stack 513 can be located above the SDAP 416. Auser datagram protocol (UDP)/transmission control protocol (TCP) stack520 can be located above the IP stack 513. A session initiation protocol(SIP) stack 522 can be located above the UDP/TCP stack 520, and can beused by the UE 102 and the UPF 134.

The General Packet Radio Service (GPRS) Tunneling Protocol for the userplane (GTP-U) layer 504 may be used for carrying user data within the 5Gcore network 120 and between the radio access network 110 and the 5Gcore network 120. The user data transported can be packets in IPv4,IPv6, or PPP formats, for example. The UDP and IP security (UDP/IP)layer 503 may provide checksums for data integrity, port numbers foraddressing different functions at the source and destination, andencryption and authentication on the selected data flows. The RAN node128/130 and the UPF 134 may utilize an N3 interface to exchange userplane data via a protocol stack comprising the L1 layer 411, the L2layer 412, the UDP/IP layer 503, and the GTP-U layer 504. As discussedabove with respect to FIG. 4, NAS protocols support the mobility of theUE 101 and the session management procedures to establish and maintainIP connectivity between the UE 101 and the UPF 134.

FIG. 6 is a block diagram illustrating components, according to someexample aspects, able to read instructions from a machine-readable orcomputer-readable medium (e.g., a non-transitory machine-readablestorage medium) and perform any one or more of the methodologiesdiscussed herein. Specifically, FIG. 6 shows a diagrammaticrepresentation of hardware resources 600 including one or moreprocessors (or processor cores) 610, one or more memory/storage devices620, and one or more communication resources 630, each of which may becommunicatively coupled via a bus 640. For aspects in which nodevirtualization (e.g., NFV) is utilized, a hypervisor 602 may be executedto provide an execution environment for one or more network slicesand/or sub-slices to utilize the hardware resources 600

The processors 610 (e.g., a central processing unit (CPU), a reducedinstruction set computing (RISC) processor, a complex instruction setcomputing (CISC) processor, a graphics processing unit (GPU), a digitalsignal processor (DSP) such as a baseband processor, an applicationspecific integrated circuit (ASIC), a radio-frequency integrated circuit(RFIC), another processor, or any suitable combination thereof) mayinclude, for example, a processor 612 and a processor 614.

The memory/storage devices 620 may include main memory, disk storage, orany suitable combination thereof. The memory/storage devices 620 mayinclude, but are not limited to, any type of volatile or non-volatilememory such as dynamic random access memory (DRAM), static random-accessmemory (SRAM), erasable programmable read-only memory (EPROM),electrically erasable programmable read-only memory (EEPROM), Flashmemory, solid-state storage, etc.

The communication resources 630 may include interconnection or networkinterface components or other suitable devices to communicate with oneor more peripheral devices 604 or one or more databases 606 via anetwork 608. For example, the communication resources 630 may includewired communication components (e.g., for coupling via a UniversalSerial Bus (USB)), cellular communication components, NFC components,Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components,and other communication components.

Instructions 650 may comprise software, a program, an application, anapplet, an app, or other executable code for causing at least any of theprocessors 610 to perform any one or more of the methodologies discussedherein. The instructions 650 may reside, completely or partially, withinat least one of the processors 610 (e.g., within the processor's cachememory), the memory/storage devices 620, or any suitable combinationthereof. Furthermore, any portion of the instructions 650 may betransferred to the hardware resources 600 from any combination of theperipheral devices 604 or the databases 606. Accordingly, the memory ofprocessors 610, the memory/storage devices 620, the peripheral devices604, and the databases 606 are examples of computer-readable andmachine-readable media.

FIG. 7 is an illustration of a per UE network controlled small gap(NCSG) in accordance with some aspects. Referring to FIG. 7, there isillustrated a plurality of subframes 700 which can be used in connectionwith per UE NCSG configuration. More specifically, the network (e.g.node 111) can communicate NCSG configuration information 141A, which caninclude durations for NCSG related processing intervals, such as avisible interruption length 1 (VIL1) period 708, a VIL2 period 712, anda measurement length (ML) period 710. In some aspects, a duration of themeasurement of the measurement gap 706 can be indicated by the NCSGconfiguration information 140A and can be equal to the durations of theNCSG related periods 708, 710, and 712.

During the example operation, UE 101 can be communicating (e.g.receiving or transmitting) data using one or more of the subframesassociated with serving carrier 702 at frequency 1. After per UE NCSGconfiguration information 141A is received (e.g., includingidentification of one or more subframes for use as a measurement gap aswell as durations of NCSG related periods 706, 708, 710, and 712) UE 101can interrupt transmission or reception of data on frequency 1 duringVIL1 period 708. The UE 101 can then retune one or more of its RF chainsto frequency 2 associated with non-serving carrier 704. For the durationof ML 710, UE 101 can perform measurements on frequency 2, whiletransmitting or receiving data (e.g., during subframes I+2 through I+5)on frequency 1 using serving carrier 702. The UE 101 can then interrupttransmission and reception on frequency 1 during the VIL2 period 712.Transmission and reception of data on frequency 1 can resume after theexpiration of the VIL2 period 712.

FIG. 8 is an illustration of NCSG patterns which can be used inconnection with per UE NCSG configuration in accordance with someaspects. Referring to FIG. 8, table 800 includes example NCSG patterns,which can be included as part of the NCSG configuration information141A. Each of the identified four NCSG patterns includes exampledurations of the VIL1 period 708, the ML period 710, the VIL2 period 712as well as a duration for an example visible interruption repetitionperiod (VIRP).

FIG. 9 is an example communication exchange for configuring per UE NCSGin accordance with some aspects. Referring to FIG. 9, the communicationexchange 900 can take place between the UE 902 and a node 904 (e.g., agNB). The UE 902 and the node 904 can perform similar functionalities asthe UE 101 and node 111 or 112 in FIG. 1A.

At operation 906, the UE 902 can communicate UE capability information908 to the node 904. For example, the UE capability information 908 caninclude a UE-EUTRA-Capability information element or UE-Capabilityinformation element. In some aspects, the UE capability information 908can include one or more fields indicating (e.g., to the gNB 904) thatthe UE supports indicating per UE NCSG configuration. In some aspects,such fields can include a per UE-NCSG-Indication field.

In some aspects, the UE capability information 908 can include one ormore fields indicating whether the UE supports measurement NCSG patternIDs 0, 1, 2, and 3 (e.g., as seen in FIG. 8). In instances when suchfield (or fields) is included and UE supports asynchronous dualconnectivity, the UE can be configured to support NCSG pattern IDs 0, 1,2, and 3. In instances when such field is included in the UE does notsupport asynchronous dual connectivity, only NCSG pattern IDs 0 and 1can be supported by UE 902.

At operation 910, node 904 can communicate NCSG indication requestinformation 912 to the UE 902. In some aspects, information 912 caninclude one or more fields (e.g., ncsgIndicationRequest field) in aconfiguration message, such as a RRCConnectionReconfiguration message orRRCConnectionResume message. In some aspects, other types ofconfiguration messages can be used to communicate information 912. Insome aspects, information 912 can indicate to the UE 902 that a specificfield or message (e.g., ncsg-needed field) can be communicated in aspecified type of response message (e.g.,RRCConnectionReconfigurationComplete message orRRCConnectionResumeComplete message) back to the node 904 in order toindicate that NCSG configuration information is needed.

At operation 914, UE 902 can communicate a request 916 for NCSGconfiguration. The request 916 can include the ncsg-needed fieldmentioned above. At 918, the node 904 can configure one or moremeasurement frequencies and associated NCSG configurations for the UE902. At operation 922, the NCSG configurations 920 (which can be thesame as the configuration information 140A in FIG. 1A) can becommunicated from the node 904 to the UE 902. At operation 924, UE 902can perform the NCSG measurements based on the NCSG configurationinformation 920. At operation 928, the NCSG measurements results 926 canbe communicated back to the node 904 for further processing. Atoperation 932, the node 904 can take one or more actions based on thecommunicated measurement results 926, such as, communicate a handovercommand 930 to the UE 902.

FIG. 10 illustrates generally a flowchart of example functionalitieswhich can be performed in connection with per UE NCSG configuration andmeasurements, in accordance with some aspects. Referring to FIG. 10, theexample method 1000 can start at operation 1002, when capabilityinformation (e.g., 908) can be encoded by the UE 101 for transmissionwithin a serving cell of an evolved Node-B (eNB) 111. The capabilityinformation can be configured to indicate that the UE 101 supports perUE network controlled small gap (NCSG) operation.

At operation 1004, a network message sent in response to the capabilityinformation, can be decoded by the UE 902. The network message canincluding an indication (e.g., 912) of a request message for requestinga per UE NCSG on a first frequency associated with the serving cell. Forexample, the NCSG indication 912 can include a fieldncsgIndicationRequest indicating to the UE that the UE can includencsg-needed field in a response configuration message (e.g., RRCconnection reconfiguration complete message or RRC connection resumecomplete message).

At operation 1006, the UE 902 can be configured to encode the requestmessage to request the per UE NCSG on the first frequency. For example,the UE 902 can encode the ncsg-needed field within the request 916(e.g., within a RRCConnectionReconfigurationComplete message or aRRCConnectionResumeComplete message) for communication to the node 904.

At operation 1008, the UE 902 can be configured to decode configurationinformation (e.g., 920 or 140A) received in response to the requestmessage. The configuration information can include a NCSG configurationfor the NCSG on the first frequency (NCSG for frequency 1 whilemeasurements are performed on frequency 2, as illustrated in FIG. 7). Atoperation 1010, the UE 902 can be configured to perform measurements ona second frequency (e.g., frequency 2 in FIG. 7) during a measurementgap (e.g., 706), where the measurement gap is configured based on theNCSG configuration (e.g., 920).

FIG. 11 illustrates a block diagram of a communication device such as anevolved Node-B (eNB), a new generation Node-B (gNB), an access point(AP), a wireless station (STA), a mobile station (MS), or a userequipment (UE), in accordance with some aspects. In alternative aspects,the communication device 1100 may operate as a standalone device or maybe connected (e.g., networked) to other communication devices.

Circuitry (e.g., processing circuitry) is a collection of circuitsimplemented in tangible entities of the device 1100 that includehardware (e.g., simple circuits, gates, logic, etc.). Circuitrymembership may be flexible over time. Circuitries include members thatmay, alone or in combination, perform specified operations whenoperating In an example, hardware of the circuitry may be immutablydesigned to carry out a specific operation (e.g., hardwired). In anexample, the hardware of the circuitry may include variably connectedphysical components (e.g., execution units, transistors, simplecircuits, etc.) including a machine-readable medium physically modified(e.g., magnetically, electrically, moveable placement of invariantmassed particles, etc.) to encode instructions of the specificoperation.

In connecting the physical components, the underlying electricalproperties of a hardware constituent are changed, for example, from aninsulator to a conductor or vice versa. The instructions enable embeddedhardware (e.g., the execution units or a loading mechanism) to createmembers of the circuitry in hardware via the variable connections tocarry out portions of the specific operation when in operation.Accordingly, in an example, the machine-readable medium elements arepart of the circuitry or are communicatively coupled to the othercomponents of the circuitry when the device is operating In an example,any of the physical components may be used in more than one member ofmore than one circuitry. For example, under operation, execution unitsmay be used in a first circuit of a first circuitry at one point in timeand reused by a second circuit in the first circuitry, or by a thirdcircuit in a second circuitry at a different time. Additional examplesof these components with respect to the device 1100 follow.

In some aspects, the device 1100 may operate as a standalone device ormay be connected (e.g., networked) to other devices. In a networkeddeployment, the communication device 1100 may operate in the capacity ofa server communication device, a client communication device, or both inserver-client network environments. In an example, the communicationdevice 1100 may act as a peer communication device in peer-to-peer (P2P)(or other distributed) network environment. The communication device1100 may be a UE, eNB, PC, a tablet PC, a STB, a PDA, a mobiletelephone, a smart phone, a web appliance, a network router, switch orbridge, or any communication device capable of executing instructions(sequential or otherwise) that specify actions to be taken by thatcommunication device. Further, while only a single communication deviceis illustrated, the term “communication device” shall also be taken toinclude any collection of communication devices that individually orjointly execute a set (or multiple sets) of instructions to perform anyone or more of the methodologies discussed herein, such as cloudcomputing software as a service (SaaS), and other computer clusterconfigurations.

Examples, as described herein, may include, or may operate on, logic ora number of components, modules, or mechanisms. Modules are tangibleentities (e.g., hardware) capable of performing specified operations andmay be configured or arranged in a certain manner. In an example,circuits may be arranged (e.g., internally or with respect to externalentities such as other circuits) in a specified manner as a module. Inan example, the whole or part of one or more computer systems (e.g., astandalone, client or server computer system) or one or more hardwareprocessors may be configured by firmware or software (e.g.,instructions, an application portion, or an application) as a modulethat operates to perform specified operations. In an example, thesoftware may reside on a communication device-readable medium. In anexample, the software, when executed by the underlying hardware of themodule, causes the hardware to perform the specified operations.

Accordingly, the term “module” is understood to encompass a tangibleentity, be that an entity that is physically constructed, specificallyconfigured (e.g., hardwired), or temporarily (e.g., transitorily)configured (e.g., programmed) to operate in a specified manner or toperform part or all of any operation described herein. Consideringexamples in which modules are temporarily configured, each of themodules need not be instantiated at any one moment in time. For example,where the modules comprise a general-purpose hardware processorconfigured using software, the general-purpose hardware processor may beconfigured as respective different modules at different times. Softwaremay accordingly configure a hardware processor, for example, toconstitute a particular module at one instance of time and to constitutea different module at a different instance of time.

Communication device (e.g., UE) 1100 may include a hardware processor1102 (e.g., a central processing unit (CPU), a graphics processing unit(GPU), a hardware processor core, or any combination thereof), a mainmemory 1104, a static memory 1106, and mass storage 1107 (e.g., harddrive, tape drive, flash storage, or other block or storage devices),some or all of which may communicate with each other via an interlink(e.g., bus) 1108.

The communication device 1100 may further include a display device 1110,an alphanumeric input device 1112 (e.g., a keyboard), and a userinterface (UI) navigation device 1114 (e.g., a mouse). In an example,the display device 1110, input device 1112 and UI navigation device 1114may be a touch screen display. The communication device 1100 mayadditionally include a signal generation device 1118 (e.g., a speaker),a network interface device 1120, and one or more sensors 1121, such as aglobal positioning system (GPS) sensor, compass, accelerometer, or othersensor. The communication device 1100 may include an output controller1128, such as a serial (e.g., universal serial bus (USB), parallel, orother wired or wireless (e.g., infrared (IR), near field communication(NFC), etc.) connection to communicate or control one or more peripheraldevices (e.g., a printer, card reader, etc.).

The storage device 1107 may include a communication device-readablemedium 1122, on which is stored one or more sets of data structures orinstructions 1124 (e.g., software) embodying or utilized by any one ormore of the techniques or functions described herein. In some aspects,registers of the processor 1102, the main memory 1104, the static memory1106, and/or the mass storage 1107 may be, or include (completely or atleast partially), the device-readable medium 1122, on which is storedthe one or more sets of data structures or instructions 1124, embodyingor utilized by any one or more of the techniques or functions describedherein. In an example, one or any combination of the hardware processor1102, the main memory 1104, the static memory 1106, or the mass storage1116 may constitute the device-readable medium 1122.

As used herein, the term “device-readable medium” is interchangeablewith “computer-readable medium” or “machine-readable medium”. While thecommunication device-readable medium 1122 is illustrated as a singlemedium, the term “communication device-readable medium” may include asingle medium or multiple media (e.g., a centralized or distributeddatabase, and/or associated caches and servers) configured to store theone or more instructions 1124.

The term “communication device-readable medium” may include any mediumthat is capable of storing encoding or carrying instructions (e.g.,instructions 1124) for execution by the communication device 1100 andthat cause the communication device 1100 to perform any one or more ofthe techniques of the present disclosure, or that is capable of storingencoding or carrying data structures used by or associated with suchinstructions. Non-limiting communication device-readable medium examplesmay include solid-state memories, and optical and magnetic media.Specific examples of communication device-readable media may include:non-volatile memory, such as semiconductor memory devices (e.g.,Electrically Programmable Read-Only Memory (EPROM), ElectricallyErasable Programmable Read-Only Memory (EEPROM)) and flash memorydevices; magnetic disks, such as internal hard disks and removabledisks; magneto-optical disks; Random Access Memory (RAM); and CD-ROM andDVD-ROM disks. In some examples, communication device-readable media mayinclude non-transitory communication device-readable media. In someexamples, communication device-readable media may include communicationdevice-readable media that is not a transitory propagating signal.

The instructions 1124 may further be transmitted or received over acommunications network 1126 using a transmission medium via the networkinterface device 1120 utilizing any one of a number of transferprotocols (e.g., frame relay, internet protocol (IP), transmissioncontrol protocol (TCP), user datagram protocol (UDP), hypertext transferprotocol (HTTP), etc.). Example communication networks may include alocal area network (LAN), a wide area network (WAN), a packet datanetwork (e.g., the Internet), mobile telephone networks (e.g., cellularnetworks), Plain Old Telephone (POTS) networks, and wireless datanetworks (e.g., Institute of Electrical and Electronics Engineers (IEEE)802.11 family of standards known as Wi-Fi®, IEEE 802.16 family ofstandards known as WiMax®), IEEE 802.15.4 family of standards, a LongTerm Evolution (LTE) family of standards, a Universal MobileTelecommunications System (UMTS) family of standards, peer-to-peer (P2P)networks, among others. In an example, the network interface device 1120may include one or more physical jacks (e.g., Ethernet, coaxial, orphone jacks) or one or more antennas to connect to the communicationsnetwork 1126. In an example, the network interface device 1120 mayinclude a plurality of antennas to wirelessly communicate using at leastone of single-input multiple-output (SIMO), MIMO, or multiple-inputsingle-output (M ISO) techniques. In some examples, the networkinterface device 1120 may wirelessly communicate using Multiple UserMIMO techniques.

The term “transmission medium” shall be taken to include any intangiblemedium that is capable of storing encoding or carrying instructions forexecution by the communication device 1100, and includes digital oranalog communications signals or other intangible medium to facilitatecommunication of such software. In this regard, a transmission medium inthe context of this disclosure is a device-readable medium.

ADDITIONAL NOTES AND EXAMPLES

Example 1 is an apparatus of a user equipment (UE), the apparatuscomprising processing circuitry, the processing circuitry configured to:encode capability information for transmission within a serving cell ofan evolved Node-B (eNB), the capability information indicating the UEsupports per UE network controlled small gap (NCSG) operation; encode arequest message to request a per UE NCSG on a first frequency associatedwith the serving cell; decode configuration information received inresponse to the request message, the configuration information includinga NCSG configuration for the NCSG on the first frequency; and performmeasurements on a second frequency during a measurement gap, themeasurement gap configured based on the NCSG configuration; and memorycoupled to the processing circuitry, the memory configured to store theNCSG configuration.

In Example 2, the subject matter of Example 1 includes, wherein theprocessing circuitry is further configured to: decode a network messagein response to the capability information, the network message includingan indication of the request message for requesting the per UE NCSG onthe first frequency.

In Example 3, the subject matter of Example 2 includes, wherein theindication of the request message is in a ncsgIndicationRequest field inthe network message.

In Example 4, the subject matter of Examples 2-3 includes, wherein thenetwork message is a radio resource control (RRC) ConnectionReconfiguration (RRCConnectionReconfiguration) message, and the requestmessage is a RRC Connection Reconfiguration Complete(RRCConnectionReconfigurationComplete) message.

In Example 5, the subject matter of Examples 2-4 includes, wherein thenetwork message is a RRC Connection Resume (RRCConnectionResume)message, and the request message is a RRC Connection Resume Complete(RRCConnectionResumeComplete) message.

In Example 6, the subject matter of Examples 1-5 includes, wherein theprocessing circuitry is configured to: encode the capability informationin UE-Evolved Universal Terrestrial Radio Access (EUTRA) Capability(UE-EUTRA-Capability) information element.

In Example 7, the subject matter of Examples 1-6 includes, wherein theNCSG configuration includes a first visible interruption length (VIL1)period, a second visible interruption length (VIL2) period, and ameasurement length (ML) period associated with the measurement gap.

In Example 8, the subject matter of Example 7 includes, wherein toperform the measurements on the second frequency, the processingcircuitry is configured to: refrain from transmitting or receiving dataon the first frequency for the duration of the VIL1 and VIL2 periods.

In Example 9, the subject matter of Example 8 includes, wherein toperform the measurements on the second frequency, the processingcircuitry is configured to: resume transmitting or receiving the data onthe first frequency during the ML period, while performing themeasurements on the second frequency.

In Example 10, the subject matter of Examples 7-9 includes, wherein thecapability information identifies one or more NCSG Patterns supported bythe UE, wherein each of the NCSG Patterns includes a pre-determinedduration of the VIL1, VIL2, and ML periods.

In Example 11, the subject matter of Example 10 includes, wherein theone or more NCSG Patterns include NCSG Pattern ID #0 and NCSG Pattern ID#1 with VIL1 period of 1 millisecond (ms) and ML period of 4 ms.

In Example 12, the subject matter of Example 11 includes, wherein theone or more NCSG Patterns include NCSG Pattern ID #2 and NCSG Pattern ID#3 with VIL1 period of 2 ms and ML period of 3 ms.

In Example 13, the subject matter of Examples 1-12 includes, wherein therequest message includes a ncsg-needed field for requesting the NCSG onthe first frequency.

In Example 14, the subject matter of Examples 1-13 includes, wherein theprocessing circuitry is configured to: decode a configuration message toinitiate handover to a second serving cell of the eNB associated withthe second frequency, based on the measurements on the second frequencyduring the measurement gap.

In Example 15, the subject matter of Examples 1-14 includes, transceivercircuitry coupled to the processing circuitry; and, one or more antennascoupled to the transceiver circuitry.

Example 16 is an apparatus of a Node-B (NB), the apparatus comprisingprocessing circuitry, the processing circuitry configured to: decodecapability information from a user equipment (UE), the capabilityinformation indicating that the UE supports per UE network controlledsmall gap (NCSG) operation; decode a request message requesting a per UENCSG on a first frequency associated with a serving cell of the NB;encode configuration information in response to the request message, theconfiguration information including a NCSG configuration for the NCSG onthe first frequency; and decode measurement information associated witha second frequency and determined during a measurement gap, a durationof the measurement gap configured based on the NCSG configuration; andmemory coupled to the processing circuitry, the memory configured tostore the NCSG configuration.

In Example 17, the subject matter of Example 16 includes, wherein theprocessing circuitry is configured to: encode a network message inresponse to the capability information, the network message indicatingthe request message for use by the UE to request the per UE NCSG.

In Example 18, the subject matter of Examples 16-17 includes, whereinthe processing circuitry is configured to: encode a configurationmessage to initiate handover to a second serving cell of the NBassociated with the second frequency, based on the measurementinformation associated with the second frequency and determined duringthe measurement gap.

In Example 19, the subject matter of Examples 16-18 includes, whereinthe NCSG configuration includes a first visible interruption length(VIL1) period, a second visible interruption length (VIL2) period, and ameasurement length (ML) period associated with the measurement gap.

In Example 20, the subject matter of Examples 16-19 includes, whereinthe NB is one of a Next Generation Node-B (gNB) or an Evolved Node-B(eNB).

Example 21 is a computer-readable storage medium that storesinstructions for execution by one or more processors of a user equipment(UE), the instructions to configure the one or more processors to causethe UE to: encode capability information for transmission within aserving cell of an evolved Node-B (eNB), the capability informationindicating the UE supports per UE network controlled small gap (NCSG)operation; decode a network message in response to the capabilityinformation, the network message including an indication of a requestmessage for requesting a per UE NCSG on a first frequency associatedwith the serving cell; encode the request message to request the per UENCSG on the first frequency; decode configuration information receivedin response to the request message, the configuration informationincluding a NCSG configuration for the NCSG on the first frequency; andperform measurements on a second frequency during a measurement gap, themeasurement gap configured based on the NCSG configuration.

In Example 22, the subject matter of Example 21 includes, wherein thenetwork message is a radio resource control (RRC) ConnectionReconfiguration (RRCConnectionReconfigiration) message, and the requestmessage is a RRC Connection Reconfiguration Complete(RRCConnectionReconfigurationComplete) message.

In Example 23, the subject matter of Example 22 includes, wherein thenetwork message is a RRC Connection Resume (RRCConnectionResume)message, and the request message is a RRC Connection Resume Complete(RRCConnectionResumeComplete) message.

In Example 24, the subject matter of Examples 21-23 includes, whereinthe instructions further cause the UE to: encode the capabilityinformation in UE-Evolved Universal Terrestrial Radio Access (EUTRA)Capability (UE-EUTRA-Capability) information element.

In Example 25, the subject matter of Examples 21-24 includes, whereinthe NCSG configuration includes a first visible interruption length(VIL1) period, a second visible interruption length (VIL2) period, and ameasurement length (ML) period associated with the measurement gap.

In Example 26, the subject matter of Example 25 includes, wherein toperform the measurements on the second frequency, the instructionsfurther cause the UE to: refrain from transmitting or receiving data onthe first frequency for the duration of the VIL1 and VIL2 periods.

In Example 27, the subject matter of Example 26 includes, wherein toperform the measurements on the second frequency, the instructionsfurther cause the UE to: resume transmitting or receiving the data onthe first frequency during the ML period, while performing themeasurements on the second frequency.

In Example 28, the subject matter of Examples 21-27 includes, whereinthe instructions further cause the UE to: decode a configuration messageto initiate handover to a second serving cell of the eNB associated withthe second frequency, based on the measurements on the second frequencyduring the measurement gap.

Example 29 is at least one machine-readable medium includinginstructions that, when executed by processing circuitry, cause theprocessing circuitry to perform operations to implement of any ofExamples 1-28.

Example 30 is an apparatus comprising means to implement of any ofExamples 1-28.

Example 31 is a system to implement of any of Examples 1-28.

Example 32 is a method to implement of any of Examples 1-28.

Although an aspect has been described with reference to specific exampleaspects, it will be evident that various modifications and changes maybe made to these aspects without departing from the broader scope of thepresent disclosure. Accordingly, the specification and drawings are tobe regarded in an illustrative rather than a restrictive sense. Theaccompanying drawings that form a part hereof show, by way ofillustration, and not of limitation, specific aspects in which thesubject matter may be practiced. The aspects illustrated are describedin sufficient detail to enable those skilled in the art to practice theteachings disclosed herein. Other aspects may be utilized and derivedtherefrom, such that structural and logical substitutions and changesmay be made without departing from the scope of this disclosure. ThisDetailed Description, therefore, is not to be taken in a limiting sense,and the scope of various aspects is defined only by the appended claims,along with the full rang of equivalents to which such claims areentitled.

Such aspects of the inventive subject matter may be referred to herein,individually and/or collectively, merely for convenience and withoutintending to voluntarily limit the scope of this application to anysingle aspect or inventive concept if more than one is in factdisclosed. Thus, although specific aspects have been illustrated anddescribed herein, it should be appreciated that any arrangementcalculated to achieve the same purpose may be substituted for thespecific aspects shown. This disclosure is intended to cover any and alladaptations or variations of various aspects. Combinations of the aboveaspects, and other aspects not specifically described herein, will beapparent to those of skill in the art upon reviewing the abovedescription.

The Abstract of the Disclosure is provided to allow the reader toquickly ascertain the nature of the technical disclosure. It issubmitted with the understanding that it will not be used to interpretor limit the scope or meaning of the claims. In addition, in theforegoing Detailed Description, it can be seen that various features aregrouped together in a single aspect for the purpose of streamlining thedisclosure. This method of disclosure is not to be interpreted asreflecting an intention that the claimed aspects require more featuresthan are expressly recited in each claim. Rather, as the followingclaims reflect, inventive subject matter lies in less than all featuresof a single disclosed aspect. Thus the following claims are herebyincorporated into the Detailed Description, with each claim standing onits own as a separate aspect.

What is claimed is:
 1. An apparatus comprising: at least one processor,the at least one processor configured to cause a user equipment (UE) to:encode capability information for transmission within a serving cell ofa base station, the capability information indicating the UE supportsper UE network controlled small gap (NCSG) operation; decode anRRCConnectionReconfiguration message or an RRCConnectionResume messageindicating that the UE can communicate a need for NCSG operation; encodea message to request a per UE NCSG on a first frequency associated withthe serving cell, wherein the message indicates that NCSG operation isneeded by the UE, wherein the message comprises anRRCConnectionReconfigurationComplete message or anRRCConnectionResumeComplete message; decode configuration informationreceived in response to the message, the configuration informationincluding a per UE NCSG configuration for the NCSG on the firstfrequency; and perform measurements during a measurement gap, themeasurement gap configured based on the per UE NCSG configuration; andmemory coupled to the at least one processor, the memory configured tostore the per UE NCSG configuration.
 2. The apparatus of claim 1,wherein the at least one processor is further configured to: decode anetwork message in response to the capability information, the networkmessage including an indication of a request message for requesting theper UE NCSG.
 3. The apparatus of claim 1, wherein the indication of therequest message is in a ncsgIndicationRequest field in the networkmessage.
 4. The apparatus of claim 1, wherein the at least one processoris configured to: encode the capability information in a UE-EvolvedUniversal Terrestrial Radio Access (EUTRA) Capability(UE-EUTRA-Capability) information element.
 5. The apparatus of claim 1,wherein the NCSG configuration includes a first visible interruptionlength (VIL1) period, a second visible interruption length (VIL2)period, and a measurement length (ML) period associated with themeasurement gap.
 6. The apparatus of claim 5, wherein to perform themeasurements, the at least one processor is configured to: refrain fromtransmitting or receiving data on the first frequency for the durationof the VIL1 and VIL2 periods.
 7. The apparatus of claim 6, wherein toperform the measurements, the at least one processor is configured to:resume transmitting or receiving the data on the first frequency duringthe ML period, while performing the measurements.
 8. The apparatus ofclaim 5, wherein the capability information identifies one or more NCSGPatterns supported by the UE, wherein each of the NCSG Patterns includesa pre-determined duration of the VIL1, VIL2, and ML periods.
 9. Theapparatus of claim 8, wherein the one or more NCSG Patterns include NCSGPattern ID #0 and NCSG Pattern ID #1 with VIL1 period of 1 millisecond(ms) and ML period of 4 ms.
 10. The apparatus of claim 1, furthercomprising: transceiver circuitry coupled to the at least one processor;and one or more antennas coupled to the transceiver circuitry.
 11. Anapparatus, the apparatus comprising: at least one processor, the atleast one processor configured to cause a base station to: decodecapability information from a user equipment (UE), the capabilityinformation indicating that the UE supports per UE network controlledsmall gap (NCSG) operation; encode an RRCConnectionReconfigurationmessage or an RRCConnectionResume message indicating that the UE cancommunicate a need for NCSG operation; decode a message from the UE torequest a per UE NCSG on a first frequency associated with a servingcell of the base station, wherein the message indicates that NCSGoperation is needed by the UE, wherein the message comprises anRRCConnectionReconfigurationComplete message or anRRCConnectionResumeComplete message; encode configuration information inresponse to the message, the configuration information including a perUE NCSG configuration for the NCSG on the first frequency; and decodemeasurement information during a measurement gap, a duration of themeasurement gap configured based on the per UE NCSG configuration. 12.The apparatus of claim 11, wherein the RRCConnectionReconfigurationmessage or the RRCConnectionResume message is encoded in response to thecapability information.
 13. The apparatus of claim 11, wherein the atleast one processor is configured to: encode a configuration message toinitiate handover to a second serving cell of the base station, based onthe measurement information and determined during the measurement gap.14. The apparatus of claim 11, wherein the NCSG configuration includes afirst visible interruption length (VIL1) period, a second visibleinterruption length (VIL2) period, and a measurement length (ML) periodassociated with the measurement gap.
 15. A non-transitorycomputer-readable storage medium that stores instructions for executionby one or more processors of a user equipment (UE), the instructions toconfigure the one or more processors to cause the UE to: encodecapability information for transmission within a serving cell of a basestation, the capability information indicating the UE supports per UEnetwork controlled small gap (NCSG) operation; decode anRRCConnectionReconfiguration message or an RRCConnectionResume messageindicating that the UE can communicate a need for NCSG operation; encodea message to request a per UE NCSG on a first frequency associated withthe serving cell, wherein the message indicates that NCSG operation isneeded by the UE, wherein the message comprises anRRCConnectionReconfigurationComplete message or anRRCConnectionResumeComplete message; decode configuration informationreceived in response to the message, the configuration informationincluding a per UE NCSG configuration for the NCSG on the firstfrequency; perform measurements during a measurement gap, themeasurement gap configured based on the per UE NCSG configuration; andstore the per UE NCSG configuration in the storage medium.
 16. Thenon-transitory computer-readable storage medium of claim 15, wherein theinstructions further cause the UE to: encode the capability informationin UE-Evolved Universal Terrestrial Radio Access (EUTRA) Capability(UE-EUTRA-Capability) information element.
 17. The non-transitorycomputer-readable storage medium of claim 15, wherein the NCSGconfiguration includes a first visible interruption length (VIL1)period, a second visible interruption length (VIL2) period, and ameasurement length (ML) period associated with the measurement gap. 18.The non-transitory computer-readable storage medium of claim 17, whereinto perform the measurements, the instructions further cause the UE to:refrain from transmitting or receiving data on the first frequency forthe duration of the VIL1 and VIL2 periods.
 19. The non-transitorycomputer-readable storage medium of claim 18, wherein to perform themeasurements, the instructions further cause the UE to: resumetransmitting or receiving the data on the first frequency during the MLperiod, while performing the measurements.
 20. The non-transitorycomputer-readable storage medium of claim 17, wherein the capabilityinformation identifies one or more NCSG Patterns supported by the UE,wherein each of the NCSG Patterns includes a pre-determined duration ofthe VIL1, VIL2, and ML periods.